> ## Documentation Index
> Fetch the complete documentation index at: https://docs.phinite.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Triggers (Autonomous Assistants)

> Configure triggers to start flows automatically or from external systems.

# Triggers

Triggers define how and when a flow begins.\
You can configure them to start automatically, on a schedule, or through external API calls.

<Frame>
  <img src="https://mintcdn.com/phinite/spbPnSZPWmAXAKhH/images/Triggers.png?fit=max&auto=format&n=spbPnSZPWmAXAKhH&q=85&s=79f6012307f86350ea15a810b38225c9" alt="Triggers" width="1919" height="872" data-path="images/Triggers.png" />
</Frame>

<Info>
  Triggers connect your assistant to external workflows and automation systems.
</Info>

***

## Trigger Types

Phinite supports three trigger types.

<Accordion title="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.
</Accordion>

<Accordion title="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.
</Accordion>

### **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

<Steps>
  <Step title="Go to Assistants → Components → Triggers." />

  <Step title="Click New Trigger." />

  <Step title="Select the Trigger Type (API, Scheduler, or Background Task)." />

  <Step title="Choose the integration, if applicable. The API URL will adjust accordingly (for example, /jira will be appended to the URL for Jira Webhook)." />

  <Step title="Choose the Target Agent Graph." />

  <Step title="Save, attach to build and test the trigger." />
</Steps>

<Card title="Tip">
  Use scheduler-based triggers for long-running workflows that may exceed standard API timeout limits.
</Card>

### Manage Triggers

| **Action** | **Description**                        |
| :--------- | :------------------------------------- |
| **Edit**   | Update type, frequency, or target flow |

## Workspace API Keys

API-based triggers depend on workspace-level API keys for authentication.

<Info>
  Store and rotate keys securely. Never expose API keys in client-side or public repositories.
</Info>

## **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.

## **Related Topics**

* [Intents](/assistants/components/intents)
* [Agent Graphs](/assistants/components/flows)