Configure connected app actions

Use a connected app action to read or update a business record from a workflow. Choose the account, supply its required inputs, and decide what happens when the action succeeds or fails. Connect the app account before selecting it in the editor.

Choose the account and action

1. Confirm the connection and required resources in Settings > Integrations.
2. In a Logic Flow add Integration action. In an Automation flow add Use connected app.
3. Choose the provider and connected account, then select an action available in that editor's catalog.
4. Review its input fields, output fields and offered outcomes before continuing.

The two editors do not expose every provider action identically. Use the catalog for the current editor and account. An integration logo or an action visible elsewhere does not grant permission here.

Map inputs and outputs

An input is a value the action needs, such as an email address. An output is a result it returns, such as a record ID. Typed means the value must use the format the field expects, such as text, a number, or a list.

Choose literal values for fixed configuration. Use the editor's value selector for trigger, contact, flow, loop-item or earlier action information where that field permits it. Select a bound spreadsheet, calendar or file through the resource control instead of guessing an identifier.

Name the result so later steps can select its declared fields. A field that expects a typed collection or prepared file needs that result type, not a text representation. Every route to this step must first run the step that creates the value.

For an illustrative enquiry record, select Google Sheets' append-row action when offered, choose the permitted spreadsheet and worksheet, and map already validated enquiry fields into the selected columns. Confirm the new row in the sheet after testing. A saved row does not confirm a reservation or payment.

Current Logic Flow consumers include selected Google Sheets row append, Google Calendar event creation and Google Drive file import when the account and catalog permit them. This is not permission to call every write action from an inbound journey.

Handle failure and uncertainty

Connect the success, failure and uncertain-result outcomes offered by the action. Use a clear customer reply or Inbox handoff when the conversation cannot continue.

A timeout can leave the result uncertain. Check the owning system before retrying an action that could create or change a record. A longer prompt or another workflow branch cannot establish whether the external system committed it.

If an action contract or permission changes, refresh the resource selection, inspect the input/output mappings, validate and republish deliberately. See custom connections for defining your own approved methods and Automation run history for investigation.