Data · Demo connector

Demo CRM

Five fictional accounts and a handful of leads, tickets and activities that workflows read and write.

Reads
  • Accounts by email domain or id
  • Existing leads
Writes
  • Leads
  • Tickets
  • Invoices
  • Candidates
  • Activities
  • Reviews
Permission scopes it would request
  • crm.accounts.read
  • crm.records.write (after approval)
In this demo

Writes land in an in-memory copy for one run and are shown as a before and after diff. The CRM outage scenario makes it return a simulated 503 four times.

In a real deployment

A real deployment would connect your own CRM with scoped credentials stored server side, never in the browser.

Try the live studio