Automations

Set it up once. It runs on its own

Triage issues every morning. Summarize pull requests when they merge. Post a daily standup digest. Your agent handles the routine work so your team doesn’t have to.

Try It Free View Pricing

Why Automations

Real AI, not just rules

Your agent works while you sleep

Automations run on schedules or in response to events. A morning briefing at 9 AM. An issue triage when new tickets come in. A weekly summary every Friday. No manual trigger needed.

Real AI, not just rules

Unlike traditional automation tools that follow if-then rules, Conduity automations are powered by your AI agent. They can reason, summarize, draft responses, and make judgment calls.

Connected to everything

Automations have access to the same integrations, knowledge base, and memory as your agents. An automation that triages issues can check the knowledge base, check calendars, and assign accordingly.

Schedules

Cron trigger examples

Expression	Meaning	Use Case
0 9 * * 1-5	Weekdays at 9:00 AM	Morning briefing, daily standup
0 17 * * 5	Fridays at 5:00 PM	Weekly summary
0 /6 * *	Every 6 hours	Monitoring check-in
0 0 1 * *	1st of each month	Monthly report
/30 * * *	Every 30 minutes	Real-time monitoring

Setup

Create an automation in 5 steps

Choose a trigger

Select cron schedule or event trigger. For cron, pick from presets or write a custom expression. For events, select the integration and event type.

Select an agent

Choose which agent runs the automation. The agent’s integrations, knowledge base, and memory are all available during execution.

Write the prompt

Describe what the agent should do when triggered. Be specific — the prompt is the instruction set.

Set output destination

Choose where results go: chat, webhook URL, or integration action (create an issue, send an email, post to Slack).

Enable

Toggle the automation on. It starts running immediately based on the trigger.

Use Cases

Automations your team will love

Morning briefing

Weekdays at 9 AM: check email for anything urgent, review your calendar, and summarize any Linear issues updated overnight.

Agent:Urgent email: Client escalation from Acme Corp about API downtime. Today’s calendar: Design review at 10 AM, Sprint planning at 1 PM. Overnight: 3 issues moved to In Review, 1 new bug report.

PR summary on merge

Triggered when a PR is closed and merged. Summarize what changed, why, and any risks.

Agent:PR #847 merged: Refactor authentication middleware. Replaced custom JWT validation with jose library. Updated 12 files. Risk: services relying on old verifyToken() export need updated imports.

Issue triage

Triggered when a new Linear issue is created. Read the description, check the knowledge base, suggest priority and assignee.

Weekly team digest

Fridays at 5 PM: compile issues completed, PRs merged, blockers mentioned in conversations, and upcoming deadlines.

Release notes

Triggered on GitHub release. Generate user-facing release notes from commits and PRs in changelog format.

Monitoring

Full visibility into every run

Every automation execution is logged with status (success, failed, skipped), trigger details, the full agent response, duration, and timestamp.

If an automation fails — expired token, rate limit hit — the run is logged with the error. Failed automations don’t retry automatically. Check run history to diagnose and re-run manually.

Disable an automation without deleting it. Re-enable anytime and it picks up where it left off based on the trigger schedule.

Plans

Limits by plan

Feature	Pro	Team	BYOK
Automations	5	Unlimited	Unlimited
Cron triggers
Event triggers

Put your agent to work — even when you’re not

5 automations on Pro. Unlimited on Team and BYOK.

Start Free Trial