Every connector asks for the narrowest scope that works

Each entry below lists the exact scopes it requests, the events it can trigger on, and the actions it can take. Scope is declared by the workflow rather than granted to your account, so two workflows sharing a connector do not share its permissions — and revoking one credential stops one workflow rather than every workflow that ever touched the integration.

Search by name or filter by category. Every card lists the triggers, actions, and scopes that connector requests.

11 connectors match

  • Gmail

    Email

    Watches a mailbox for messages matching a server-side filter, extracts fields through a redaction pass before any model call, and drafts or sends replies in the same thread. Attachments are hashed and scanned, never retained past the run.

    Triggers
    • New email matching filter
    • Label applied to thread
    • Attachment received from external domain
    Actions
    • Send reply in thread
    • Create draft for approval
    • Apply label and archive
    Requested scopes
    • gmail.readonly
    • gmail.send
    • gmail.labels
  • Google Workspace

    Productivity

    Resolves approvers against your directory so escalations follow a real reporting line, writes run artefacts to a nominated Drive folder, and books calendar holds for change windows. Directory reads are cached for fifteen minutes, never mirrored.

    Triggers
    • User added to group
    • File shared outside organisation
    • Calendar event created
    Actions
    • Resolve approver from directory
    • Write run report to Drive folder
    • Create calendar hold for change window
    Requested scopes
    • admin.directory.user.readonly
    • drive.file
    • calendar.events
  • Slack

    Messaging

    Posts run summaries and approval prompts to a named channel, then records the approve or reject decision as a signed event bound to the acting user ID. A rejection halts the workflow and stays in the audit log permanently.

    Triggers
    • Message posted in channel
    • Emoji reaction added
    • Slash command invoked
    Actions
    • Post approval request with buttons
    • Send run summary to channel
    • Open incident thread and pin context
    Requested scopes
    • chat:write
    • channels:read
    • reactions:read
  • WhatsApp Business

    Messaging

    Sends template notifications to customers and reads inbound replies for opt-out keywords in English, Hindi, and Tamil. Phone numbers are tokenised before an AI step runs, so the model receives a reference rather than a subscriber identity.

    Triggers
    • Inbound message received
    • Delivery status changed
    • Opt-out keyword detected
    Actions
    • Send approved template message
    • Mark conversation resolved
    • Record opt-out on contact
    Requested scopes
    • whatsapp_business_messaging
    • whatsapp_business_management
  • Razorpay

    Payments

    Listens for payment, refund, and settlement events, verifies the signature on each callback, then reconciles amounts in ₹ against your ledger before anything downstream fires. Refunds above a configurable ₹ threshold always route to human approval.

    Triggers
    • Payment captured
    • Payment failed
    • Refund processed
    • Settlement credited
    Actions
    • Issue refund after approval
    • Fetch payment detail for reconciliation
    • Tag order as disputed
    Requested scopes
    • payments.read
    • refunds.write
    • settlements.read
  • Shopify

    Commerce

    Reads new orders and fulfilment updates, enriches each with a summary of buyer notes, and writes tracking numbers back to the order. Customer addresses stay masked in run logs and drop out when the retention window closes.

    Triggers
    • Order created
    • Order cancelled
    • Inventory below threshold
    Actions
    • Write fulfilment and tracking
    • Add order note from AI summary
    • Tag high-risk order for review
    Requested scopes
    • read_orders
    • read_inventory
    • write_fulfillments
  • Zoho CRM

    CRM

    Creates and updates leads, contacts, and deals from upstream triggers, using a field map you review before the first live run. Duplicate checks match on email and phone hash, so a retried run cannot silently fork a record.

    Triggers
    • Lead created
    • Deal stage changed
    • Contact field updated
    Actions
    • Create or update lead
    • Move deal to stage
    • Attach run transcript to record
    Requested scopes
    • ZohoCRM.modules.leads.CREATE
    • ZohoCRM.modules.deals.UPDATE
    • ZohoCRM.settings.fields.READ
  • Google Sheets

    Productivity

    Appends rows, reads named ranges, and drives lookups for teams already running on a shared sheet. Writes are idempotent by row key, and any sheet holding personal data can be flagged so redaction applies before an AI step.

    Triggers
    • New row added
    • Cell value changed in watched range
    Actions
    • Append row with run result
    • Read range as lookup table
    • Update cell by row key
    Requested scopes
    • spreadsheets.readonly
    • drive.file
  • Meta Lead Ads

    Ads

    Pulls new lead form submissions within seconds, deduplicates by form and email, then routes qualified leads to your CRM or a WhatsApp follow-up. Raw form payloads survive only for the audit window you configure, then are purged.

    Triggers
    • New lead form submission
    • Campaign spend threshold reached
    Actions
    • Score lead against qualification rules
    • Forward lead to CRM
    • Queue first-touch message
    Requested scopes
    • leads_retrieval
    • pages_show_list
    • ads_read
  • REST API

    Developer

    A signed JSON API for starting runs, reading status, and pulling audit records into your own SIEM. Tokens are scoped per workflow, expire on a schedule you set, and every call is recorded against the caller identity.

    Triggers
    • POST /v1/runs received
    • Scheduled poll of /v1/runs?status=awaiting_approval
    Actions
    • Start run with signed payload
    • Fetch run status and risk score
    • Export audit log page
    Requested scopes
    • runs:write
    • runs:read
    • audit:read
  • Webhooks

    Developer

    Accepts inbound events from any system that can sign a request, with HMAC verification, replay protection across a five-minute window, and per-endpoint rate limits. Rejected payloads are logged with the reason, so a failure is never silent.

    Triggers
    • Signed inbound event received
    • Signature verification failed
    • Replay window violation
    Actions
    • Dispatch outbound event with HMAC header
    • Replay stored delivery
    • Rotate endpoint signing secret
    Requested scopes
    • events:receive
    • signature:verify
    • replay:write

All third-party product names, logos, and brands are the property and trademarks of their respective owners, used here for identification only. Reference to them does not imply any partnership, sponsorship, endorsement, or official status.

A connector that asks for full account access is a connector you cannot reason about during a review. Every scope in this catalogue is listed in plain text before you authorise it, and adding a step that needs a wider one triggers a fresh consent naming the specific addition rather than silently inheriting what was granted last time.

Integrations

What next

A connector you need is missing

The catalogue reflects what is built rather than what is planned, so there is no roadmap page listing connectors that do not exist. Tell us which system you need and what the workflow has to do with it, and we will tell you whether the REST connector already covers it.