- Documentation
- Workflows
- Workflow Nodes
- Trigger nodes
Trigger nodes
Choose the trigger that should start a TaskJuice workflow run.
Triggers start workflow runs. Choose one trigger when the workflow should begin, then configure the selected trigger definition.
Supported triggers
| Trigger | Best for | Notes |
|---|---|---|
| Form Submission | Intake forms, approvals, customer requests | Starts when a published TaskJuice form is submitted. |
| Schedule | Recurring jobs | Runs every configured number of minutes, hours, days, or cron schedule. |
| Webhook | Real-time external events | Exposes a unique URL for another system to call. |
| App Webhook | Provider events from connected apps | Uses app-specific webhook subscriptions when available. |
| Polling | Apps without outbound webhooks | Checks a source on an interval and starts runs for new items. |
| RSS | Feed-based workflows | Starts from new feed entries. |
| Stream | Message or event stream consumption | Starts from stream events configured by the integration. |
| Call Workflow | Reusable workflow entry points | Lets another workflow invoke this workflow. |
| Error Handler | Recovery paths | Starts when configured workflow failures occur. |
Production guidance
- Use Form Submission for structured human intake.
- Use Webhook when a source can call TaskJuice immediately.
- Use Polling only when the source cannot push events.
- Use Schedule for time-based workflows that do not depend on a source event.
- Add authentication, filters, and deduplication before sending production webhook traffic.
Related pages
Was this helpful?