Use Automations when you want Pod to run a Skill automatically instead of launching it manually every time. An automation checks the records in scope on a recurring interval, evaluates your trigger condition, and runs the selected Skill when the condition matches.

Automation results appear in Agent Feed, and you can also send successful runs to Slack when Slack delivery is enabled.

You can also start from a Skill card. Open Agents -> Skills, then click Add Trigger on the Skill you want to automate.

If you still need to create the Skill first, start with Build a new Skill or Build your first Skill from the Library.

The Automations page has two tabs:

Use the status filter to show All, Active, or Inactive automations.

If you need to edit the underlying Skill, click Manage Skills to return to the Skills page.

To create an automation:

If you start from a Skill card with Add Trigger, Pod skips the Skill picker and opens the same trigger configuration flow for that Skill.

When you create an automation from the Automations page, Pod asks you to choose a Skill first.

The picker shows:

If no Skills are available, create or import a Skill first from Agents -> Skills.

Use Recurring Interval to choose how often Pod should check the records in scope.

Options include:

For daily and weekly automations, choose the time of day. For weekly automations, choose the day of the week. For custom automations, choose the number of hours or days between checks.

Pod shows the timezone it will use for the schedule.

Use Trigger Condition to describe, in plain English, when the Skill should run.

You do not need formulas, CRM code, or special syntax. Write the condition the same way you would explain it to a teammate.

Good examples:

Keep the trigger condition focused on which records should run. Keep the Skill prompt focused on what the AI Agent should produce when it runs.

Before saving, use Preview trigger runs to estimate how many runs your condition would create.

Pod shows a message like:

This trigger will run 12 agents across 20 records in scope

If the condition would run on most records in scope, Pod highlights the preview so you can tighten the condition before saving.

Previewing is especially useful when you are creating a broad automation or testing a new trigger condition.

Use Send to Slack when you want a Slack DM after a successful automatic run.

Slack delivery is on by default for new automations. In practice, the Slack message includes a short run summary and a link back to Pod where you can review the full result and approve or reject any pending actions.

Slack delivery requires setup:

If something is missing, Pod shows an inline message telling you what to fix.

Use the Active / Inactive switch to control whether the automation should run after it is saved.

Leave it Active when the automation is ready to start. Set it to Inactive if you are still testing the condition or want to save the configuration without running it yet.

You can also turn an automation on or off later from its automation card.

Return to Agents -> Automations when you need to update an automation.

From an automation card, you can:

Use the status filter to narrow the list to All, Active, or Inactive automations.

Results from automated runs appear in Agent Feed. Use Agent Feed when you want to review what ran, open the related deal, and take action on the output.

Automated runs can also create pending actions, such as email drafts or CRM updates. These actions wait for your approval before Pod completes them.

Related places to review results:

Automations are most useful when you want Pod to watch for recurring workflow moments without needing to remember to launch the Skill manually.

Common examples include:

Need help? Send us a message via the in-app chat or email us at [email protected].

Want to talk to someone? Book a session with one of our specialists.