Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt

Use this file to discover all available pages before exploring further.

Automation templates are the fastest way to get useful automation running in Custory. Instead of starting with a blank workflow, you begin with a pattern that already reflects a common product-ops use case and then adjust the destination, scope, and wording for your team.

​
Why templates matter

Most smaller teams do not fail at automation because they lack ideas. They fail because setting up the first good workflow takes too much attention. Templates reduce that setup tax. They help you start from:
  • A useful trigger
  • A sensible action sequence
  • Strong default AI instructions
  • A clear platform combination

​
How templates work

When you choose a template, Custory creates an automation draft. That draft still needs your decisions:
  • Which workspace integration to use
  • Which journey or journeys to scope
  • Which channel, repo, project, or team to target
  • Whether the AI instructions need adjustment
Think of a template as a high-quality starting point, not a fully finished workflow.

​
Template categories in Custory

Custory currently includes template families across four practical themes.

​
Team updates

These templates help teams keep journey work visible in Slack or Discord. Examples include:
  • Active team member for Slack
  • Active team member for Discord
  • Weekly journey pulse for Slack
  • Weekly journey pulse for Discord
  • Daily focus check for Slack
  • Daily focus check for Discord
Use them when the problem is not lack of insight, but lack of consistent visibility and follow-through.

​
Journey freshness

These templates bring external signals back into the journey and then notify the team. Examples include:
  • PostHog event drift to Slack
  • PostHog event drift to Discord
  • PostHog top events discovery to Slack
  • PostHog top events discovery to Discord
These are strong for product-led teams that want behavior signals to refresh the journey continuously instead of living only in analytics dashboards.

​
Focus sequences

These templates combine task creation with communication. Examples include:
  • Priority focus: Slack + Linear
  • Priority focus: Slack + Jira
  • Priority focus: Discord + Linear
  • Priority focus: Discord + Jira
  • Quick wins: Slack + Linear
  • Quick wins: Slack + Jira
  • Quick wins: Discord + Linear
  • Quick wins: Discord + Jira
These are useful when the team wants one change in Custory to trigger both:
  • A concrete execution artifact
  • A visible team prompt

​
Shipping signals

These templates connect delivery events back to journey maintenance. Examples include:
  • GitHub merged PR journey refresh to Slack
  • GitHub merged PR journey refresh to Discord
These are particularly useful for smaller product teams that ship quickly and want the journey to stay current without manual review after every merge.

​
Template details

​
Active team member

Purpose:
  • Review a scoped journey regularly
  • Surface what changed
  • Highlight stale areas
  • Suggest the next actions
Best for:
  • Founder-led review rhythms
  • Weekly product check-ins
  • Teams that need a lightweight accountability loop

​
Weekly journey pulse

Purpose:
  • Summarize new items, status changes, stale assumptions, and blocked work
Best for:
  • Weekly product or support review
  • Team-wide visibility without opening the journey in every meeting

​
Daily focus check

Purpose:
  • Inspect high-priority and high-impact items
  • Suggest what deserves attention today
Best for:
  • Small teams that need quick alignment without running full planning rituals every morning

​
PostHog event drift

Purpose:
  • Detect movement in a key event
  • Update the journey with the new signal
  • Notify the team with a useful interpretation
Best for:
  • Activation
  • Retention
  • Conversion
  • Feature adoption reviews

​
PostHog top events discovery

Purpose:
  • Turn surprising product usage patterns into candidate journey insights
Best for:
  • Teams that want analytics to influence discovery work, not just dashboard review

​
Priority focus

Purpose:
  • Turn a newly high-priority opportunity or solution into an issue and a team prompt
Best for:
  • Teams that want faster movement from prioritization into execution

​
Quick wins

Purpose:
  • Route high-impact, low-effort items into action before they go stale
Best for:
  • Lean teams that need obvious wins to move quickly without a heavy planning cycle

​
GitHub merged PR journey refresh

Purpose:
  • Use merged PR context to update the journey
  • Surface what changed
  • Prompt for customer validation where needed
Best for:
  • Fast-moving product teams where shipped changes outpace manual journey maintenance

​
How to choose the right template

Start with the smallest workflow that closes a real gap. Good first choices:
  • 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

​
What to customize after selecting a template

Always review:
  • Scope
  • Trigger cadence or threshold
  • Channel or task destination
  • Journey update instructions
  • AI-written wording
Templates are strong defaults, but your team still needs to decide what “good enough automation” looks like.

​
Common mistakes

​
Installing too many templates at once

Start with one or two workflows the team will actually pay attention to.

​
Leaving destination fields unset

A draft is not useful until the channel, repo, team, or project is configured correctly.

​
Automating before the journey data is trustworthy

Automations amplify the quality of the underlying context. If statuses, owners, or priorities are stale, clean that up first.