Integration action reference

An integration action is one operation against a connected system, such as quickbooks.createInvoice or plaid.syncTransactions. This section lists the actions for each system. For the plain-language view, see Connect your systems.

How an action is named

An action id is <module>.<action>. The module is the block type (quickbooks, netsuite, sage-intacct), and the action is the operation id from the block's Action list. A few older module ids still resolve: sageIntacct, zohoInventory and dropboxSign.

How a step selects an action

An action step sets type: "action", the action id and its settings in config. Studio also stores the operation id in config.operation.

{
  "id": "create_invoice",
  "type": "action",
  "name": "Create invoice",
  "action": "quickbooks.createInvoice",
  "config": {
    "operation": "createInvoice",
    "connection": "<quickbooks-connection-id>",
    "realmId": "9341454792746027",
    "customerId": "{{steps.find_customer.id}}",
    "lines": [{ "description": "Consulting services", "amount": 1500 }]
  }
}

• config.connection pins one stored connection (the connection row id). Without it, most systems use the company's default connection for that provider. Finances (Plaid) steps require a pin; Avalara and Plaid steps stop instead of falling back when a pinned connection no longer resolves.
• Read a step's result in later steps with {{steps.<id>.<path>}}. Each system page shows the output shape.
• Put credentials in company secrets and reference them as {{secrets.KEY}}, not as literals.

Studio list and engine actions

For most systems, every action the engine can run is in the Studio Action list. NetSuite, Xero, Sage Intacct and Rillet also have actions the engine runs that are not in that list. Each of those pages marks which actions are which. POST /api/v1/workflows/validate checks against the Studio list, so it reports the extra ones as UNKNOWN_OPERATION, even though they run.

Connection methods

Live catalog

The catalog endpoints read the deployed registry, so they are the source of truth for field names and the action list.

Send x-api-key with a key that has workflows:read (blocks) or connections:read (integrations). See Block and action discovery and Connections.

Systems

Payment, CRM, document, file and messaging systems have their own pages in this section, such as Stripe and Slack.