Bring Masnet events into HubSpot through an intermediary

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.

Architecture

1. Choose the intermediary and configure its reception with the corresponding guide: n8n, Make, Zapier, MuleSoft or one of the code verification guides.
2. Enter the intermediary URL in Destination address (https) in Masnet.
3. In the intermediary, verify the signature and only then call HubSpot.

Writing to HubSpot

The CRM API v3 creates a contact with POST https://api.hubapi.com/crm/v3/objects/contacts and a JSON body with properties (and associations); it answers 201 with the created object. Other objects follow the same pattern in the HubSpot API reference. Authentication is configured according to the HubSpot authentication documentation.

{
  "properties": {
    "email": "[email protected]",
    "firstname": "Example",
    "lastname": "Surname"
  },
  "associations": []
}

Masnet events are about contracts, guarantees, tenders and other management objects, not contacts. Define custom properties in HubSpot to store, for example, the Masnet identifier and the contract code, and map from data.object. The property names are a decision of your organization.

Response

The intermediary answers 2xx to Masnet after verifying the signature and queuing the work. The call to HubSpot must be made asynchronously.

Testing with the test event

1. Send the test from Masnet with Test destination and Send test.
2. Check that the intermediary verifies the signature and does not write to HubSpot for com.masnet.integration.test.v1.

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: