Tip
Use scheduler-based triggers for long-running workflows that may exceed standard API timeout limits.
Triggers (Autonomous Assistants)
Triggers define how and when a flow begins.
You can configure them to start automatically, on a schedule, or through external API calls.
Trigger Types
Section titled “Trigger Types”Phinite supports three trigger types.
1. API-Based Trigger (2 types)
API-based triggers allow external applications to start a specific flow.
Use Case
- When you need real-time activation from an external event such as a form submission or webhook.
Configuration
- Requires an API key defined at the workspace level.
- Called via an HTTP POST request.
Best For Fast, real-time executions where the response completes within seconds.
2. Scheduler-Based Trigger
Scheduler-based triggers start flows at fixed intervals or specific times.
Use Case
Use this for periodic automation such as daily reports, nightly data syncs, or batch processing.
Configuration
- Define a start time and recurrence (hourly, daily, weekly, or custom cron).
- Ideal for long-running flows that might exceed API timeouts.
Best For
Background processes that do not require immediate response.
Choose the Right Trigger
Section titled “Choose the Right Trigger”| Scenario | Recommended Trigger | Reason |
|---|---|---|
| External app sends an event that needs immediate action | API-Based | Instant activation with minimal latency |
| Recurring process such as reports or sync tasks | Scheduler-Based | Prevents timeout and automates repetition |
Configure a Trigger
Section titled “Configure a Trigger”-
Go to Assistants → Components → Triggers.
-
Click New Trigger.
-
Select the Trigger Type (API, Scheduler, or Background Task).
-
Choose the integration, if applicable. The API URL will adjust accordingly (for example, /jira will be appended to the URL for Jira Webhook).
-
Choose the Target Agent Graph.
-
Save, attach to build and test the trigger.
Manage Triggers
Section titled “Manage Triggers”| Action | Description |
|---|---|
| Edit | Update type, frequency, or target flow |
Workspace API Keys
Section titled “Workspace API Keys”API-based triggers depend on workspace-level API keys for authentication.
Best Practices
Section titled “Best Practices”- Use API triggers for short, transactional events.
- Use Background task for long events (track via status api).
- Use Scheduler triggers for recurring jobs.
- Avoid attaching multiple triggers to the same flow unless needed.
- Test each trigger thoroughly in the development environment before deploying to production.