Webhooks

Webhooks allow Makinari to notify your own systems in real-time when important events occur.

When to use

• You want to sync new leads generated by the Sales agent into your external CRM (like Salesforce or HubSpot).
• You want to alert a Slack channel when a high-value customer sends a message on the website chat.
• You want to update your database when a Requirement is completed.

Configuring Webhooks

Currently, webhooks are configured via the Makinari API or support team. (A dashboard UI for webhooks is in development).

To register a webhook, you need:

• An endpoint URL on your server that accepts POST requests.
• A list of events you want to subscribe to.

Common Events

• lead.created: Emitted when the Sales agent or tracking script identifies a new lead.
• message.received: Emitted when a user sends a message via Chat, WhatsApp, or Email.
• requirement.status_changed: Emitted when an AI Goal moves from planning to execution to completed.
• campaign.completed: Emitted when an outbound campaign finishes sending.

Security and Verification

Makinari secures webhooks by signing the payload. When your server receives a webhook, it should verify the signature to ensure the request actually came from Makinari.

1. Makinari sends a signature in the x-makinari-signature header.
2. The signature is an HMAC-SHA256 hash of the request body, signed using your Site’s Webhook Secret.
3. Your server must compute the HMAC of the raw request body using the same secret and compare it to the header.

If the signatures match, you can trust the payload.

Inbound provider webhooks (platform)

These hit Makinari, not your app. Each route validates the provider signature — no API key.

Outbound x-makinari-signature above is for your subscriber URL (webhooks tool). Do not reuse a provider secret there.