App action nodes
Use app action nodes to read from and write to connected business systems.
App action nodes call supported app APIs from a workflow. They are the right choice when the workflow needs to create, update, search, send, or retrieve records in another system.
Supported action coverage
TaskJuice seeds action definitions for these app families:
| App family | Examples of workflow use |
|---|---|
| Forms | Pause for a form response and resume the workflow. |
| GitHub | Create or update engineering records. |
| Gmail | Send or process email. |
| Google Calendar | Create and update calendar events. |
| Google Drive | Work with files and folders. |
| Google Sheets | Add, update, or search spreadsheet rows. |
| HubSpot | Create or update CRM records. |
| QuickBooks | Work with accounting records. |
| Salesforce | Create or update CRM records. |
| Shopify | Work with commerce records. |
| Slack | Send messages and notifications. |
| Strava | Work with activity data. |
| Stripe | Work with payments and billing records. |
| Twilio | Send communication events. |
| Workday | Work with HR records. |
Configure an app action
Choose an app
Open the Add Node panel and select the app that owns the operation.
Choose an action
Pick the action that matches the business task, such as creating a record or sending a message.
Select a connection
Choose the connection the workflow should use. Workspace-scoped workflows can only use connections available to that workspace.
Map fields
Map trigger or upstream node output into the required action fields.
Test before publishing
Run a test and confirm the app received the expected data.
When to use HTTP Request instead
Use HTTP Request when an app action does not exist yet, when you need to call an internal API, or when you are prototyping a custom integration.
Prefer a first-party app action when one exists. It gives builders a clearer configuration surface and keeps provider-specific behavior out of workflow expressions.