Automation
Zapier + AutomateNexus CRM
Trigger Zaps from twelve CRM events and write records back through the REST API.
Zapier, wired into your pipeline.
- 01
Signed webhooks in, REST API out
AutomateNexus CRM connects to Zapier through Webhooks by Zapier: a Catch Hook receives CRM events the moment they happen, and a POST step writes records back through the REST API with your API key.
- 02
Twelve events to trigger on
New and updated contacts, companies, customers and tasks, deals created, updated or moved between stages, and form submissions, each ticked per webhook so a Zap only hears what it needs.
- 03
The whole record, every time
Each delivery carries the full record as it now stands and, for updates, the record as it was, so a Zap can branch on an old and new stage without calling the API again.
Connected in three steps.
- Step 01
Create a Catch Hook in Zapier
In a new Zap choose Webhooks by Zapier → Catch Hook and copy the URL Zapier shows you.
- Step 02
Create the webhook in the CRM
Under Settings → Integrations → Developer → Webhooks, name it, paste the URL, tick the events and click Create webhook. Copy the signing secret; it is shown once.
- Step 03
Test, then map your actions
Click Test on the webhook (or create a real record) so Zapier sees a sample payload, then add your action steps. To write back, use Webhooks by Zapier → POST against your API endpoint with an Authorization: Bearer header.
Built to be left alone.
Retries you can see
A failed delivery is retried after 1, 5 and 30 minutes, four attempts in all with a 10-second timeout each. The delivery log keeps the last 50 deliveries for 30 days with status, response code, response time and the exact payload sent.
Signed, rotatable secrets
Every delivery carries an X-Webhook-Signature header (t=timestamp, v1=HMAC-SHA256 of the timestamp and raw body). The secret is shown once, stored encrypted, and can be rotated from the webhook's row.
120 requests a minute
The REST API allows 120 requests a minute per key and answers 429 with a Retry-After header beyond that. Webhooks and full API access are on all four plans.
Twelve events out, the whole API in.
Out of the CRM: twelve events
Tick any of contact.created, contact.updated, deal.created, deal.updated, deal.stage_changed, customer.created, customer.updated, company.created, company.updated, task.created, task.updated and form.submitted. Each payload carries the event, when it happened, your organization id, the full record as it now stands and, for updates, the record as it was, so Zapier can compare a deal's old and new stage without another call.
Into the CRM: the REST API
Create, read, update and delete /contacts, /customers, /deals, /tasks, /notes and /invoices, plus /search, /bulk, /export, /analytics and /schema, with Authorization: Bearer YOUR_API_KEY. The API Documentation page (Docs button next to your API endpoint) lists every payload.
The quick-send URL
For simple 'send data to the CRM' steps, each platform card under Settings → Integrations → Automation shows an inbound URL ending in /webhooks/zapier. POST an event_type and a data object with your key in an x-api-key header; it accepts contact.created, contact.updated (matched by email or id), deal.created, customer.created and activity.created, and stamps Zapier as the record's source.
What Zapier can and cannot do here.
No app in the Zapier directory
The setup is a webhook URL and an API key, not a one-click authorisation. It works on every Zapier plan that includes Webhooks by Zapier and on every AutomateNexus CRM plan.
Automation inside the CRM first
The workflow builder sends email and SMS, creates tasks, logs activities and calls webhooks without Zapier; booking workflows do the same on Booking Created, Confirmed, Cancelled, Rescheduled or Completed. Use Zapier when the other end lives outside the CRM.
Keys you can retire
API keys are created under Settings → Integrations → Developer → API keys and shown in full once; afterwards only the prefix is displayed. Administrators can also issue scoped keys with a 30-day, 90-day or one-year expiry under Settings → API keys, and delete any key to revoke it.
Zapier and AutomateNexus CRM, answered.
No. AutomateNexus CRM does not publish an app in the Zapier directory. You connect with Webhooks by Zapier's Catch Hook for triggers and its POST step for actions, which takes a webhook URL and an API key rather than a one-click authorisation, and works on every plan.
Twelve: contact.created, contact.updated, deal.created, deal.updated, deal.stage_changed, customer.created, customer.updated, company.created, company.updated, task.created, task.updated and form.submitted. You choose them per webhook under Settings → Integrations → Developer → Webhooks, and a Test button sends a real, signed webhook.test delivery so Zapier can learn the payload shape.
Through the REST API with an API key from Settings → Integrations → Developer → API keys: POST or PUT to your API base URL plus /contacts, /deals, /tasks and the other resources, JSON body, Authorization: Bearer header. For simple inserts the quick-send URL takes an event_type and a data object with the key in an x-api-key header.
Endpoints must be HTTPS. Each delivery is signed with HMAC-SHA256 over the timestamp and raw body (the X-Webhook-Signature header, t= and v1=), the secret is generated server-side and shown once, and you can rotate it at any time; the old secret stops working immediately.
The delivery is retried after 1, 5 and 30 minutes (four attempts, 10-second timeout each). The webhook row shows consecutive failures and the time of the last success and failure, and the delivery log keeps 50 deliveries for 30 days.
Usually not. The built-in workflow builder and booking workflows send email and SMS, create tasks, log activities and call webhooks on their own; reach for Zapier when the other end of the automation lives outside the CRM.
Put Zapier to work.
Start your 7-day free trial and connect Zapier on day one. No credit card, no middleware.