Skip to main content
The Templates view offers 12 repeatable workflows across Code review, Issues & delivery, Repository health, and Reports & upkeep. Describe your workflow in the prompt field above the cards, or select a card to load a short starter there. Edit the prompt and select Continue setup to open the automation setup conversation. Selecting a template alone does not start a session or save an automation. Felan checks the team’s current event catalog, asks for missing decisions such as repository scope or schedule timezone, then summarizes the proposed configuration. No automation is created until you confirm whether to save it paused or activate it. This is conversational approval, not a new server-enforced permission control.

​
Templates

Current examples include:
  • Code review: review incoming pull requests, review code for security risks, triage pull-request feedback.
  • Issues & delivery: triage new bug reports or tracker issues, verify deployments.
  • Repository health: summarize recent CI failures, find test-coverage gaps, check repository health overnight.
  • Reports & upkeep: summarize the week in code, review dependencies, find stalled pull requests.
Template prompts describe the future work; choose its trigger during setup. Felan checks which event types are enabled for the team before using them. If an integration is missing, it explains the limitation instead of inventing a trigger.

​
Your automations

Use Your automations to manage persistent scheduled and event-triggered work. A workflow started from a template or custom request is saved here only after you confirm its configuration.

​
Configure a background automation

Click New automation to open the simple manual form: name the automation, choose one or more triggers, and write its instructions. Create automation saves it using the enabled or paused state of its triggers. This is separate from template/custom guided setup. The manual form has no setup preview and does not expose repository or environment settings.

​
Guided setup and execution context

Selecting a template fills the prompt; submitting it with Continue setup starts the setup conversation. Submitting a custom request starts the same conversation. Felan checks available connected events, asks for missing details, then asks you to confirm the proposed configuration and whether to save it paused or active. Schedules can be recurring or one-time. Event triggers use an enabled event from a connected integration, can include filters, and multiple triggers run when any one matches. Guided setup/API can also include repository scope and a team environment-variable profile. Repository scope is task context, not a permission boundary; environment profiles reuse team configuration and are not isolated execution environments. The manual editor preserves existing repository/environment settings but does not expose them for editing. Results go to the team’s default communication channel when configured; there is no per-automation destination. Otherwise they remain available in Felan. Numeric per-run usage estimates are not available. Instructions do not enforce read-only or approval permissions. Review the configured integrations and agent capabilities before activating tasks that could make consequential changes. A prompt asking for human review is not a runtime permission control. Editing through the manual form preserves current trigger status. You can pause or activate saved automations from the list.

​
Manage automations

The automation list shows each workflow’s status, trigger summary, and instructions. From the list you can:
  • Pause or activate an automation (completed one-time triggers remain terminal).
  • Edit its name, instructions, or triggers. Repository/environment settings aren’t editable in the manual form and remain unchanged when you save.
  • Delete the automation and all triggers it contains.
One-time schedules are shown as Once at with their configured timezone. After dispatching a one-time schedule, Felan marks it completed; it does not recur. To rearm it, edit its timestamp. Recurring schedules continue from their next cron occurrence.

​
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.