What it does
A schedule trigger fires on a recurring cadence you define — for example, every Monday at 9am, or every weekday at 5pm. It’s the source to reach for whenever you want Swan to do something on a timer rather than in response to an event: compiling a weekly outreach digest, posting a pipeline summary to Slack, or checking in on a list of accounts on a regular cadence.Timing
Swan checks for due schedules roughly every 5 minutes, so a fire happens within about 5 minutes of the time you scheduled — not to-the-second. If you need something to happen at a precise moment, build in a small buffer rather than relying on exact timing. To keep any single organization from overwhelming the system, scheduled trigger runs are limited to 50 fires per 10-minute window per organization. This only matters if you have a large number of schedule triggers overlapping in the same short window — for a typical handful of digests and reports, you won’t come close to it.Cost
Each fire costs 1 credit as a flat fee, plus whatever credits the run’s own actions use (enrichment, CRM writes, sending a Slack message, and so on). See credits for how action costs are calculated.Setting one up
Create one from New trigger → Schedule on Triggers (or go straight tohttps://agent.getswan.com/triggers/new). When you create a schedule trigger, you pick the cadence (frequency, days, and time), write the instructions for what to do each time it fires, and choose the toolkits it’s allowed to use. To change the schedule later, open the trigger and use its Configuration card. If the schedule becomes invalid for some reason, the trigger is automatically disabled rather than left in a broken, silently-failing state — check monitoring runs if a schedule trigger appears to have stopped firing.