Integrations

Connect SIMCOAI to what you already use.

Send bookings, orders, refunds, escalations and customers into Zapier with no code, sync a CRM with one call per contact, or build your own connection with API keys and signed webhooks.

Zapier, no codeCRM bridge
Sixteen Zapier triggers, two creates and a searchUse least-privilege API accessKeep provider secrets server-side
Send SIMCOAI records into Zapier or your own systems.
Send SIMCOAI records into Zapier or your own systems.
Approved connections

API and webhook work

Use SIMCOAI API keys and approved webhooks for customer workflows that have been reviewed for authentication, rate limits, logging, data minimisation and support ownership.

  1. Create a scoped SIMCOAI API key in the dashboard.
  2. Confirm the customer data fields that may be sent to SIMCOAI.
  3. Test with safe sample records before connecting live workflows.
  4. Review logs and disable access when a supplier, employee or workflow changes.
Provider readiness

Connector infrastructure is gated

New provider connectors are released once credentials, security, data mapping and support processes have been confirmed, so everything you can switch on is fully supported.

Provider secrets

Credentials stay on the server and are never exposed in browser code.

Entitlements

Your Stripe billing status and account sign-in state decide whether an account may use a paid integration surface.

Webhooks and API

Custom workflows require approved developer use cases and safe test data first.

Webhooks

Send signed workflow events to your systems

Add an HTTPS endpoint in Integrations → Workflow API messages to receive signed events for refunds, bookings, escalations and orders. Verify the X-SIMCOAI-Signature header, and only run an external refund or booking when payload.workflow.shouldExecuteExternalAction is true. Full details are in the API guide.

No code

Zapier and the CRM bridge

Most integrations do not need a developer. Zapier covers sixteen triggers - every stage of a booking, order, refund, escalation and customer - plus two creates ("Log an Order", "Add or Update a Customer") and a search ("Find a Customer"), so a Zap can act on SIMCOAI as well as react to it. It connects today using Zapier's own built-in Webhooks app; a dedicated SIMCOAI app for Zapier's own picker is being finished.

Building your own sync instead? The CRM bridge returns a customer and everything attached to them - their bookings, orders, refunds and escalations - in one call, with a since parameter so a nightly job reads only what changed.

Sixteen triggers

Named after the real event, not the table - a booking fires as requested, confirmed, cancelled or completed.

Two creates, one search

Log an order, add or update a customer, or look one up - the same scoped API key either way.

Only the documented fields

Internal columns are never sent - a Zap forwards whatever it is given to another company’s system, so the allow-list is what leaves SIMCOAI.

AI models

SIMCOAI-managed AI models

SIMCOAI manages all AI provider credentials centrally — you never add or manage API keys. All AI runs on SIMCOAI Intelligence. In the dashboard under AI Models you choose a model profile (Economy, Fast, Balanced or Premium) and a routing mode (Fixed or Auto by enquiry). All AI usage runs on SIMCOAI-managed infrastructure and is metered through your plan, add-ons and pay-as-you-go caps. Premium models consume premium usage units: Pro includes a limited premium allowance, and other plans use the Premium AI Models add-on and PAYG.

Safety

Integration safety rules

Only connect tools your business is authorised to use. Keep admin permissions tight, remove old connections and review logs when customer data flows between systems.

  • Use least-privilege integration access where possible
  • Do not connect test stores to live customer workflows
  • Avoid sending payment card numbers into AI prompts or logs
  • Disable integrations when a supplier, employee or workflow changes