Start Node

Every workflow begins with a Start node. It defines when and how the workflow is triggered.

Trigger types

Manual trigger

The simplest option for testing. Click Run and optionally provide input data. Manual runs are ideal during development.

Webhook trigger

1. Set trigger type to Webhook.
2. Choose the HTTP method (GET, POST, PUT, PATCH, DELETE).
3. Copy the generated webhook URL from the configuration panel.
4. Configure authentication:
   • None — open endpoint (use carefully)
   • API Key — caller must send your key in a header
   • Bearer Token — caller must send a bearer token

The request body becomes available as {{inputs}} for downstream nodes.

Example — trigger via curl:

curl -X POST YOUR_WEBHOOK_URL \
  -H "Content-Type: application/json" \
  -d '{"customer": "Acme Corp", "amount": 1500}'

Schedule trigger

1. Set trigger type to Schedule.
2. Enter a cron expression (e.g. 0 9 * * * for every day at 9:00 AM).
3. Set the timezone (defaults to UTC).

The Start node name updates to reflect the schedule (e.g. "Every Morning (9am)").

App trigger

1. Set trigger type to App.
2. Select the app (Gmail, Slack, etc.).
3. Choose the event (e.g. "Email Received").
4. Connect your account via OAuth when prompted.

The event payload is available as {{inputs}} for downstream nodes.

Agent trigger

Used with the AI agent chat sidebar. The Start node acts as the entry point when the agent initiates or continues a workflow on your behalf.

Response mode (webhook)

For webhook triggers, configure how TogoFlow responds to the caller:

• Return the last node's output as JSON
• Return a custom response body
• Return immediately (async execution)

Tips

• Use Manual while building, then switch to Webhook or Schedule for production.
• Webhook URLs are unique per workflow — don't share them publicly without authentication.
• For app triggers, ensure the app account stays connected in your organization settings.