Developers
Developer integrations
Last updated 7 November 2026
These guides show you how to connect your Insites application to other services. Data can leave your instance when something happens on your site, and other systems can call back into your instance when their data changes.
Two directions
Out of your instance
- An API Call Notification sends an HTTP request to another service when an event happens, such as a form submission.
- You set the endpoint, headers and body with Liquid, so you control exactly what is sent.
Into your instance
- A webhook from a module, such as a CRM field update, calls an endpoint you build on the instance.
- That endpoint runs your own logic, often in a background job.
Guides in this section
| Page | Use it to |
|---|---|
| Integrations Overview | See how integrations work and the common pattern for any service with a REST API |
| Third-Party Integrations | Follow a step-by-step guide for ActiveCampaign, Mailchimp, SendGrid, Sendinblue or Slack |
| Running Custom Logic from a CRM Field Update | Run your own code when a CRM field changes, using a webhook and a background job |
The common pattern
- Get API credentials from the other service.
- Store them on the instance as constants and read them with
context.constants, never in a template. - Create an API Call Notification with the endpoint, headers and body.
- Attach it to the form or event that should trigger it.
- Submit a test and check the response, which you can write to the instance log with the
logtag.
Common mistakes
- Putting an API key directly in a Liquid template. Anyone with access to the code can read it.
- Doing slow work inside a webhook request. Hand it to a background job and return quickly.
- Testing only on production. Build and test the integration on a staging instance first.