AI automations & scheduling
Give Picrowd AI a standing instruction and a trigger, and it runs on its own: on a schedule, as a heartbeat, when a ping comes due, or when a checklist completes.
What automations are
An automation is a standing instruction you hand to Picrowd AI that runs on its own when its trigger fires. Instead of asking the AI to do something once, you save the request and let it repeat.
Automations store the instruction, never a frozen result, so each run reflects the current state of your project.
How a run works
Each run executes as the person who created the automation and re-checks that person’s permissions every time. If a run needs to make changes, it still goes through the normal AI proposal-and-approval flow rather than writing silently.
Four kinds of trigger
- Scheduled: every second, minute, hour, day, week, month, or year, on weekdays or specific days, ending on a date or after a number of runs
- Heartbeat: a repeating check that quietly does nothing on uneventful runs and speaks up when something changed
- Ping automations: the commands attached to a ping run when the ping comes due
- Progress completions: run when a Progress checklist on a record reaches 100%
Good uses
- A morning digest of what changed and what is due
- Recurring follow-up checks on stale or overdue records
- Weekly summaries posted to Board
- A follow-up note and a new ping when a reminder comes due
- Routine tidy-ups or status sweeps you would otherwise do by hand
Workflows
A workflow chains several steps into one automation with a bounded schedule. Picrowd verifies a workflow before it is activated, so a broken step is caught before it runs unattended.
Notifications and nudges
When an automation has something worth your attention, the AI pill glows and shows a nudge card so results are not lost in a busy workspace. Nudges are capped per day so automations stay helpful rather than noisy. Settings → Notifications can also send them to your device.
Guardrails
Automations run within the creator’s access and AI quota, destructive actions still require confirmation, and there are limits on how many recurring jobs a person can set, so automation adds convenience without giving anything unattended write access.