The Action node performs operations in third-party apps — send an email, create a spreadsheet row, post to Slack, and hundreds of other actions.
Setup
- Drag an Action node onto the canvas.
- Click Select App and choose from the integration catalog.
- Choose an Action (e.g. Gmail → Send Email).
- Fill in the required fields, using
{{template}}syntax for dynamic values. - Connect your account when prompted (OAuth or API key).
Authentication
Actions require credentials for the target app:
| Auth type | How to connect |
|---|---|
| OAuth 2.0 | Click "Connect" and authorize via Google, GitHub, etc. |
| API Key | Enter your key in the action configuration or organization settings |
| Bearer Token | Provide a token for services like Telegram bots |
If credentials are missing when the workflow runs, you'll see an Authentication Required dialog with a Connect button.
Configuring action fields
Each action has its own fields. Common patterns:
To: {{lastOutput.email}}
Subject: New order from {{inputs.customerName}}
Body: {{lastOutput.summary}}
Use the Variables button to insert paths from upstream nodes instead of typing them manually.
Available apps
TogoFlow supports a wide integration catalog including:
Communication — Gmail, Slack, Discord, Telegram, Microsoft Teams, SendGrid, Mailgun
Google Workspace — Sheets, Calendar, Drive, Docs, Slides
Developer — GitHub, GitLab, Stripe, Vercel, Netlify, Supabase
Productivity — Notion, Airtable, Linear, Jira, Asana, Trello, Monday.com
CRM & Sales — HubSpot, Salesforce, Pipedrive
Data — PostgreSQL, MongoDB
E-commerce — Shopify, WooCommerce
Browse the full list in the Action node's app picker. Availability of specific actions depends on the app — each app exposes its own set of triggers and actions.
App triggers vs actions
- App Trigger (on the Start node) — workflow starts when something happens in the app
- Action (on the Action node) — workflow performs an operation in the app mid-flow
You can combine both: trigger on a new Gmail message, process it with AI, then post to Slack.
Tips
- Test with a Manual trigger first to verify field mappings before going live.
- For Gmail and Google apps, use OAuth — it's more secure than pasting tokens.
- Check the Execution Data tab if an action fails; the error message usually indicates a missing field or expired credential.
See Connecting Apps for detailed auth setup.