Receive Masnet events in Zapier

Requirements in Masnet

Before configuring the receiving system, prepare the destination in Masnet. The steps are the same for every system.

1. Open Company › Integrations (the Spanish interface labels it Empresa › Integraciones), go to the Destinations tab and select New destination. If the integration has no authorized data yet, Masnet asks you to authorize it first.
2. In Destination address (https) enter the receiver public URL. It must be https, port 443 or 8443 and a public DNS name: user information in the URL, fragments, IP addresses and internal names are not accepted. A query string is allowed; Masnet treats the whole URL as a credential.
3. In Format choose Standard JSON (application/json) or Structured CloudEvents (application/cloudevents+json). The event content is the same; see Webhooks.
4. Select Create destination. Masnet shows the signing secret (whsec_…) only once. Store it immediately in the receiver secret store; it cannot be read again.
5. Select Test destination and then Send test. The integration is activated only after a successful test; then use Activate destination.

Zap configuration

1. Create a Zap with the Webhooks by Zapier trigger and the Catch Raw Hook event. Per the Zapier documentation, it delivers the request body uninterpreted (up to 2 MB) and includes the headers; the Catch Hook trigger does interpret the body.
2. Copy the webhook URL into Destination address (https) in Masnet. The URL is a credential.
3. The names of the output fields (body and headers) are shown when you test the trigger; use them exactly as they appear.

Signature verification

The signature is v1, followed by base64(HMAC-SHA256) computed with the binary key obtained by base64-decoding what follows whsec_, over the bytes webhook-id + . + webhook-timestamp + . + the exact body. Always verify over the received bytes, before parsing the JSON.

Add a Code by Zapier step and pass as inputs the uninterpreted body, webhook-id, webhook-timestamp, webhook-signature and the secret. Compute the signature with the algorithm of the rule above; if the step does not support the standard cryptography modules or cannot obtain the original bytes, do not replace it by rebuilding the JSON.

The availability of libraries in the code step and the maximum execution time depend on your plan and were not verified here. If you cannot verify in Zapier, delegate to a service of your own with the Node.js or Python guide.

Response

Zapier answers the webhook request by itself. Confirm with the test event that Masnet records a 2xx code and does not depend on the result of the following steps.

Testing with the test event

1. In the Zap editor, leave the trigger waiting for a request.
2. In Masnet, select Test destination and Send test.
3. Zapier shows the received request; check the body and header fields there.

Operation: duplicates and ordering

• Idempotency. webhook-id identifies the event and is kept across retries and redeliveries. Record the identifiers already processed and discard repeats with a 2xx response.
• Ordering. Each resource (subject) carries an increasing sequence. Discard an event whose sequence is lower than or equal to the last one applied for that subject. Events of different resources have no order between them.
• Retries. Masnet retries any non-2xx response for up to 72 hours; the full schedule is in Webhooks.
• Secret rotation. When rotating with overlap, the previous secret stays valid for 24 hours and webhook-signature carries two v1,… signatures separated by a space. Accept the event if either one matches.

Troubleshooting

Masnet records the response code of each attempt in the delivery history. These are the effects of each receiver response: