Triggers
A trigger creates a task for an employee. An employee can have many triggers. Each one sets what starts the work, which inputs the task receives and who owns the result.
Trigger types
Section titled “Trigger types”| Trigger | Starts a task when | Example |
|---|---|---|
| Chat | Someone writes to the employee in the Orqane chat or on a channel: Slack, Teams, WhatsApp, voice. | @Ada, summarize this thread. |
| Schedule | A time is reached, once or on a recurring schedule. | Every Monday at 08:00, prepare the pipeline report. |
| Incoming email | An email arrives at the employee’s own address, or matches a rule in a shared inbox. | An invoice sent to ap@acme.orqane.email |
| Webhook | An outside system calls the employee’s webhook URL. | Your website posts a new demo request. |
| Business event | A connector reports an event in one of your apps. | A HubSpot deal moves to Closed won. A Zendesk ticket is tagged refund. |
| Employee request | Another employee hands off work or delegates a sub-task. | The support employee asks the finance employee to check an invoice. |
| A2A request | An agent outside Orqane sends a request over A2A. | A partner’s procurement agent asks for a quote. |
The Chat and Employee request triggers are on by default. Add the others on the employee’s Triggers tab.
Add a trigger
Section titled “Add a trigger”Open the Triggers tab
On the employee’s profile, open Triggers and click Add trigger.
Choose the type
Pick a trigger type. For business events, pick the connector and the event, such as Salesforce > Opportunity updated.
Write the task template
Describe the task the trigger creates. Use variables from the event, such as {{email.subject}} or {{deal.amount}}, to fill in the goal and inputs.
Set the owner and priority
Choose who receives the result. By default, it’s the employee’s human manager for schedules and events, and the sender for chat and email.
Add filters and save
Add filters if needed, then click Save. Click Test to send a sample event and see the task it creates, without starting a run.
Trigger filters
Section titled “Trigger filters”Filters decide which events create a task. All conditions must match.
| Filter | Example |
|---|---|
| Field value | deal.amount is greater than 10000 |
| Sender | Email from a domain in your customer list, or from a member |
| Content | Subject contains invoice or facture |
| Time window | Only between 08:00 and 19:00, Monday to Friday |
| Rate | At most 50 tasks per hour from this trigger |
| Classifier | The employee reads the event and decides if it’s relevant, using a short instruction such as “Only real support requests, not newsletters.” |
Events that don’t pass the filters are listed in the trigger’s Skipped log for 7 days, with the reason.
Deduplication
Section titled “Deduplication”The same event can arrive more than once: a webhook retried by its sender, an email forwarded twice, two employees asking for the same thing. Orqane deduplicates triggers so they don’t create duplicate tasks.
- By event ID. Events with the same source ID, such as an email
Message-IDor a webhook delivery ID, within 24 hours create one task. - By key. Set a Deduplication key on the trigger, such as
{{ticket.id}}. While a task with the same key is open, new events are added to that task as inputs instead of creating a new one. - Across employees. If two triggers create the same task for the same employee, the second is merged into the first.
Merged and dropped events appear in the task’s Activity.
Who can trigger an employee
Section titled “Who can trigger an employee”Each trigger is subject to the employee’s access rules, on the Triggers tab under Who can ask:
- Members: everyone in the workspace, specific teams, or specific people.
- External senders: for email, WhatsApp and voice, an allowlist of addresses, domains or phone numbers. Others receive a polite refusal, or are handed off to a human.
- Employees and agents: which employees can send requests, and which A2A agents are allowed.
Requests from outside your workspace are always checked by guardrails for prompt-injection attempts before a task is created.