Connectors
30 services, 100 operations. Each connector is one definition, shipped as a PHP package with Laravel integration, a Node package, a React package and a Python package, and every operation is also a fancy-flow node.
One connector, every runtime
A connector is one third-party service, such as Stripe, Gmail or Twilio, defined once and generated into four packages that share one version. They are installed, not vendored: a copied file cannot be upgraded, and third-party APIs change. None of them uses the provider's SDK; they speak plain HTTP on top of fancy-connector-core.
PHP, with Laravel
The operations for PHP 8.4+, plus a service provider, a facade and <Service>::fake() when Laravel is present.
particle-academy/<slug>-phpNode
The same operations for a Node or TypeScript backend.
@particle-academy/<slug>-jsReact
The editor surface for the connector's flow nodes, on every host.
@particle-academy/<slug>-uiPython
The operations for Python 3.11+, with no runtime dependencies.
fancy-<slug>What every connector gives you
The same capabilities in every runtime, because each package is generated from the same definition.
Verified webhooks
A trigger declares how its deliveries are checked: an HMAC signature over the raw body, or a token shared with the provider. fancy-connector-core verifies it before your code runs. 8 of the 9 triggers in the catalogue declare a check; the rest are polled, so there is no delivery to forge.
<Service>::fake() for tests
In Laravel, Stripe::fake() answers every call from the connector's own faker and records it, so a test sends nothing. Then assertSent, assertNotSent, assertNothingSent and assertSentCount. Every operation ships that faker in every runtime, as a node's fake mode.
One Google connection for the organization
Every Google connector declares the same grant: one OAuth client, one consent and one refresh token per person, with each feature's scopes asked for when it is first used. Revoking removes the whole Google grant, and the account is identified by the id_token's sub, never by email.
Laravel integration in the PHP package
An auto-discovered service provider, config under connectors.<slug> with credentials from the environment or per call, and a facade: GoogleSheets::call('append', [...]) runs any operation. Laravel is suggested, never required.
Every operation is a fancy-flow node
Each action, search and trigger has a node kind, such as @particle-academy/stripe_payment_intent, and each runtime package carries what runs it. The React package is the node's editor surface on every host.
A setup wizard per connector
Set up opens one step at a time: who does it, what to open, what to copy for your app, and how you know it worked. A step for your agent is one prompt with a Copy button.
Every connector
The catalogue this site serves at /r/connectors/index.json, which the fancy-ui MCP's list_connector_services reads too. Every package version below was checked against its registry when the index was built.
30 connectors
Facebook Lead Ads
alphaFacebook lead, Facebook lead
Gmail Inbox
alphaList Gmail mailbox history, List Gmail labels, Stop watching a Gmail mailbox, Watch a Gmail mailbox, Gmail message, List Gmail messages, Gmail message received, Gmail thread
Google Calendar
alphaGoogle Calendar stop watching, Google Calendar watch, Create Google Calendar event, Delete Google Calendar event, Google Calendar event, Google Calendar events, Update Google Calendar event, Google Calendar change
Google Docs
alphaBatch update a Google Doc, Google Docs document, Insert text into a Google Doc, Replace text in a Google Doc
Google Drive
alphaGoogle Drive file, List Google Drive files, Google Drive folder, Share a Google Drive file
Google Meet
alphaList conference records, List participants, Create meeting space, Get meeting space, List transcript entries, List transcripts
Google Sheets
alphaBatch update a Google Sheet, Google Sheets row, Read Google Sheets values, Write Google Sheets values
Google Slides
alphaBatch update a Google Slides presentation, Google Slides presentation, Google Slides presentation, Replace text in a Google Slides presentation
HubSpot
alphaCreate company, Get company, List companies, Search companies, Update company, Create contact, Get contact, List contacts, Search contacts, Update contact, HubSpot CRM event, Create deal, Get deal, List deals, Search deals, Update deal, List owners, List deal pipelines, List property definitions
Instagram for Business
alphaInstagram media container, Publish Instagram media
Microsoft Outlook
alphaOutlook calendar change, Outlook calendar event, Outlook calendar events, Outlook subscription, Outlook subscription removal, Outlook subscription renewal
Resend
alphaGet attachment, List attachments, Get received email, Email received, Send email
Slack
alphaSlack button click, Slack message, Slack message update, Slack user lookup by email
Stripe
alphaStripe customer, Stripe payment, Stripe refund, Stripe event
Install one
A PHP or Python app installs the React package for the editor and its own runtime package; it never needs the Node one.
How it fits
fancy-connector-core is the runtime every connector is built on: typed delivery, failure classification, retries, delivery verification and the choice between fake, sandbox and live. fancy-flow runs the nodes.
Install
npm install @particle-academy/fancy-connector-corenpm install @particle-academy/fancy-flow
The packages
The connector runtime: typed delivery, failure classification (unreachable / refused / ambiguous / rejected), retries, and sandbox-vs-live selection. Every connector is built on it.
Headless workflow engine + an optional React Flow editor — built-in trigger, logic, data, AI, human-in-the-loop and terminal nodes, a topological executor, and a FlowRunnerUx flow→UX bridge. The editor designs graphs; `/engine` runs them with zero React on a server, worker, or CLI (runtime twins: fancy-flow-php, fancy-flow-py).
Connect a service
Pick a connector, open its setup, and follow it one step at a time. Then put its operations in a workflow.

