Record Masnet events in Dynamics 365 with Logic Apps

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.

Receiving in Logic Apps

Configure the receiving flow as described in the Azure Logic Apps and Power Automate guide: HTTP request trigger, sig= URL in Destination address (https) and signature verification in a function before writing to Dataverse.

Verification and writing

1. After the verification, use a condition on triggerOutputs()['headers']['masnet-event-type'] to choose the branch by event type.
2. To avoid duplicates, store webhook-id in a column of the row and query it before writing; if it already exists, end without changes. If your table defines an alternate key, the Dataverse *upsert* operation avoids that step.
3. To avoid regressions, store the last applied sequence per subject and discard the event if the received one is lower than or equal to it.
4. Write to Dataverse with the connector action or with the web API: POST [Organization URI]/api/data/v9.2/<entity set> creates a row and answers 204 with the OData-EntityId header.

Mapping example: contract.status_changed

The table and column names below are an example: they correspond to a custom table that your organization must create. The Masnet fields are those of the com.masnet.contract.status_changed.v1 event, inside data.object.

Response

Answer 200 or 202 from the flow after verifying the signature. If writing to Dataverse is slow, separate receiving from processing with a queue so that you answer within 15 seconds.

Testing with the test event

1. In Masnet, select Test destination and Send test.
2. Check that the branch for the test event (com.masnet.integration.test.v1) ends without writing to Dataverse.
3. Try a real write after activating the destination, with a contract from a test environment.

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: