Automation templates

Automation templates give you a prebuilt starting point. Pick the workflow pattern, then choose the destination, scope, cadence, and wording that fit your team. Workspace owners and editors can start from templates. If you do not see Browse templates or Use template, ask a workspace owner to update your role or create the draft with you. You can open the template browser from the automations empty state or from Browse templates on the automations page.

What a template creates

When you choose a template, Custory creates an automation in draft status. The draft can include:

trigger settings
journey scope, when the template starts from a journey
one or more actions
empty integration, channel, project, team, repository, or event fields that you must fill in
AI instructions or static templates used by the actions

Templates are not ready to activate until the required fields are set.

Template library

Custory shows separate cards for Slack and Discord variants where the workflow posts a message, and Linear and Jira variants where the workflow creates a delivery task.

Pattern	Use it when	Trigger	Action	Destinations
Active team member	You want Custory AI to review a scoped journey and keep the team aware of important changes.	Weekly schedule	Posts what changed, what looks stale, top next actions, and one team question.	Slack or Discord
Weekly journey pulse	The team needs a weekly recap of journey movement.	Weekly schedule	Summarizes new items, status changes, stale assumptions, blocked work, and a recommended decision.	Slack or Discord
Daily focus check	The team wants a short daily priority prompt.	Daily schedule	Inspects high-priority and high-impact journey items and asks the team to confirm focus.	Slack or Discord
PostHog event drift	A key product event should update journey evidence when it changes.	Daily schedule	Pulls PostHog event-volume-change data, updates the journey, and posts a summary.	PostHog plus Slack or Discord
PostHog top events discovery	Product-usage patterns should become candidate insights.	Weekly schedule	Pulls top PostHog events, updates insights where relevant, and posts a summary.	PostHog plus Slack or Discord
Priority focus	Newly high-priority work should become a delivery task.	Item priority crosses `High` for opportunities or solutions	Creates a Jira or Linear issue and posts a team prompt.	Slack or Discord plus Jira or Linear
Quick wins	High-impact, low-effort work should not go stale.	Item impact reaches `4` or higher with effort `2` or lower for opportunities or solutions	Creates a Jira or Linear issue and posts a team prompt.	Slack or Discord plus Jira or Linear
GitHub merged PR journey refresh	Shipped product changes should update the journey when they affect customer experience.	GitHub pull request merged	Updates journey items when relevant and posts what changed.	GitHub plus Slack or Discord

Required setup

Before activating a template, fill in the destinations and source fields the draft cannot know yet.

Destination type	Configure	Notes
Slack	integration, channel, message wording or AI instructions	Required for Slack message actions.
Discord	integration, channel, message wording or AI instructions	Required for Discord message actions.
Jira	integration, project, issue type, summary, description, priority	Required for Jira issue actions.
Linear	integration, team, title, description, priority	Required for Linear issue actions.
GitHub	integration, repository and optional branch filters	Required for merged-PR triggers.
PostHog	integration, preset settings, event names or result limit	Required for PostHog analytics actions.

Good first templates

Start with the smallest automation that closes a real gap:

Weekly journey pulse if the problem is visibility
Priority focus if the problem is follow-through
GitHub merged PR journey refresh if the problem is journey drift after shipping
PostHog event drift if the problem is analytics staying disconnected from prioritization

Setup checks

Before activating a template:

Confirm the integration is connected.
Choose the narrowest journey or repository scope that will work.
Set the destination channel, project, repo, or team.
Review AI-written output instructions.
Save the draft.
Use Run once when the trigger is time-based and you want to inspect the result first.

Limits

Templates create drafts, not active automations.
Empty integration and destination fields must be completed before activation.
PostHog event-drift templates need at least one event name.
GitHub templates need at least one repository.
Template output depends on the quality of the journey data and AI instructions you leave in the draft.

Next step

Read Automations for triggers, filters, actions, AI-assisted editing, run history, and activation behavior.

AI features

Journey automations

What a template creates

Template library

Required setup

Good first templates

Setup checks

Limits

Next step

​What a template creates

​Template library

​Required setup

​Good first templates

​Setup checks

​Limits

​Next step

What a template creates

Template library

Required setup

Good first templates

Setup checks

Limits

Next step