Connectors

Protocols & Custom Connectors

AS2

Signed, encrypted B2B document exchange with cryptographic delivery receipts (MDNs)
Signs in with
Connection details
Runs on
Cloud or On-Prem Worker
Operations
1
Ready-made triggers
0

Connect AS2

  1. In Neblex open Connect › Connections and click New Connection.
  2. Search for AS2 and give the connection a clear name.
  3. Fill in the fields. Secret values are encrypted and never shown again.
  4. Click Test, then Create Connection.
If the system is only reachable inside your network, choose an On-Prem Worker under Test from and run the flow on that Worker. See On-Prem Workers.
FieldWhat to enter
Partner URLRequiredExample: https://as2.partner.example/receive
Our AS2 IDRequiredThe identifier your organization uses in this relationship (AS2-From).
Partner AS2 IDRequired
Our certificate (PEM)RequiredThe certificate the partner registered for you; travels in signed messages.
Our private key (PKCS#8 PEM)RequiredSecret
Partner certificate (PEM)RequiredUsed to encrypt to the partner and to verify their signatures and receipts.
Sign messagesOptional
Encrypt messagesOptional
Require signed MDNsOptionalRequest and require a detached-signed synchronous MDN independently of whether the business message itself is signed.
HTTP Basic usernameOptionalOptional transport-level HTTP Basic authentication required by some AS2 endpoints.
HTTP Basic passwordOptionalSecret
mTLS client certificate (PEM)OptionalOptional client certificate when the partner authenticates AS2 over mutual TLS.
mTLS client private key (PEM)OptionalSecret
Private CA certificate (PEM)OptionalOptional CA certificate for a partner endpoint issued by a private PKI.

Use it in a flow

  1. Open a flow, open the node library and search for AS2.
  2. Drag it onto the canvas and choose an Operation and your connection.
  3. Map the operation's fields from earlier steps, or click Map with Matt.
  4. Use Test this step to see what it returns, then save.

To start a flow from AS2 without a ready-made trigger: a Poll for changes trigger can check one of its list operations on a schedule and pass on only what is new; if AS2 can send webhooks, a Webhook trigger receives them at its own URL.

Operations

1 operations in 1 groups. Each one is a step you can add to a flow.

Message1
Send a documentsendApply the partner profile's signing and encryption choices to byte-exact business data, POST it, and verify the synchronous MDN signature, disposition, correlation, and content MIC.