Zapier

Send what SIMCOAI takes on the phone into the apps you already use, without writing anything.

What

What this is for

Every booking, order, refund, escalation and new customer SIMCOAI records can start a Zap. A Zap is a rule you build by picking from lists - "when a new booking comes in, add a row to my spreadsheet" - so this needs no developer and no code.

Put bookings straight into Google Calendar or a spreadsheet.
Post escalations into a Slack or Teams channel so nothing waits for somebody to check the dashboard.
Add every new customer to Mailchimp, HubSpot or a CRM.
Send refund requests to whoever approves them.

Setup

Connecting your account

Create an API keyIn your dashboard, open Account → API Keys and create one. Give it read access to whichever records you want to send. It is shown once - copy it before you close the page.
Add SIMCOAI in ZapierChoose SIMCOAI as your trigger app and paste the key when Zapier asks to connect.
Pick a triggerChoose from the list below and Zapier will show you real data from your account to map fields against.
Turn the Zap onSIMCOAI pushes each event as it happens. There is no polling delay.

Triggers

What can start a Zap

Each of these fires the moment the record is created or changed.

Trigger	When it runs
New booking request	The assistant takes a booking on a call or from your website.
Booking updated	A booking is confirmed, moved or cancelled.
New order	An order is logged.
Order updated	An order changes status.
New refund request	A refund request is taken. It never means money has moved - approving a refund is a separate step you control.
Refund updated	Somebody approves, declines or completes a refund.
New escalation	Something is passed to a person: a complaint, a callback request, or anything the assistant would not handle itself.
New customer	Somebody new is recorded for the first time.
Customer updated	A customer record changes.

Fields

What each trigger sends

A deliberately short, stable set. Internal columns are never sent - a Zap forwards whatever it is given to another company’s system, so only the fields below leave SIMCOAI.

{
  "id": "9f2c1e40-5b7a-4c2f-9c3d-1a2b3c4d5e6f",
  "created_at": "2026-08-19T14:32:07.114Z",
  "status": "requested",
  "customer_name": "Emily Carter",
  "customer_email": "emily.carter@example.com",
  "customer_phone": "+447700900456",
  "service_name": "Haircut",
  "preferred_time": "2026-08-21T13:30:00.000Z",
  "example": false
}

Test

Building a Zap before you have any real records

Zapier will not let you finish a trigger without sample data, and a brand new account has no bookings yet. SIMCOAI sends a clearly marked example so you can still map your fields.

An example row carries "example": true and uses a reserved address and phone number that cannot reach anybody. Once you have real records, SIMCOAI sends those instead and the flag is false. If you want a Zap to ignore examples, add a Zapier filter on that field.

Manual

Doing the same thing without Zapier

The same subscriptions are plain HTTP, so you can drive them from anything.

# List the triggers you can subscribe to
curl -s https://api.simcoai.co.uk/v1/zapier/triggers \
  -H "Authorization: Bearer $SIMCOAI_API_KEY"

# Subscribe: SIMCOAI POSTs the record to your URL when it happens
curl -s -X POST https://api.simcoai.co.uk/v1/zapier/subscribe \
  -H "Authorization: Bearer $SIMCOAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"hookUrl":"https://example.com/hooks/simcoai","event":"booking.created"}'

# Stop it again
curl -s -X DELETE https://api.simcoai.co.uk/v1/zapier/subscribe/SUBSCRIPTION_ID \
  -H "Authorization: Bearer $SIMCOAI_API_KEY"

Safe

Two things worth knowing

Subscribing twice is safe. The same URL and trigger reuses the existing subscription rather than creating a second one, so a retry cannot make every booking arrive twice.
A Zap can only do what the key can do. Scopes are checked on every request, so a read-only key cannot be turned into a write by going through Zapier.