Skip to main content
Automations start Felan sessions without a teammate manually entering the same request each time. Every automation has a name, plain-language instructions, and one or more triggers.

​
Create an automation

1

Open Automations

Select Automations in the team sidebar, then New automation.
2

Name the workflow

Use a name that makes its purpose recognizable in the automation list and session history.
3

Add triggers

Add at least one trigger. A schedule can recur from a cron expression or run once at a selected date and time in its timezone. An event trigger uses an event type available from the team’s integration configuration. One automation can contain multiple triggers.
4

Write the instructions

Describe the outcome Felan should produce when any trigger fires. These plain-language instructions become the agent task prompt.
5

Create the automation

Save it as active when at least one trigger is enabled. Triggered runs appear as sessions with automation origin information.
One-time schedules are shown as Once at with their configured timezone. After a successful run they become completed and do not recur. Recurring schedules continue from their next cron occurrence. To rearm a completed one-time schedule, edit its timestamp; the completed trigger is not reactivated by an unrelated group toggle or edit.

​
Manage automations

The list shows each automation’s state, trigger summary, trigger details, and instructions. From the list you can:
  • Pause or activate the automation (completed one-time triggers remain terminal)
  • Edit its name, instructions, or triggers
  • Delete the automation and all triggers it contains

​
Write effective instructions

Include the target, evidence to inspect, expected output, and important boundaries.
Provider event triggers require the corresponding integration and event type to be available to the team. Configure external services under Integrations, then review whether their webhook setup is automatic or manual. Custom provider and event types can be configured through the REST API and delivered through the generic webhook endpoint.