> ## 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 > Start from compact automation patterns for recurring updates, analytics signals, delivery handoff, and GitHub-driven journey refreshes. 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. ## Use a template When you choose a template, Custory creates an automation draft. Before activating it, review: * workspace integration * journey or repository scope * channel, repo, project, or team destination * trigger cadence or threshold * AI instructions and output wording Templates are strong defaults, not finished automations. ## Workflow patterns Use these patterns instead of choosing from separate Slack, Discord, Jira, and Linear copies of the same idea. | 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. | Scheduled daily or weekly | AI reviews the journey, highlights changes, flags stale areas, and suggests next actions. | Slack or Discord | | Weekly journey pulse | The team needs a weekly recap of what changed and what needs attention. | Weekly schedule | Summarizes new items, status changes, blocked work, and stale assumptions. | Slack or Discord | | Daily focus check | The team wants a short morning prompt instead of a full planning ritual. | Daily schedule | Inspects high-priority and high-impact items and posts today's shortlist. | Slack or Discord | | Analytics signal change | PostHog or Stripe movement should update the journey instead of staying in a dashboard. | Analytics or metric change | Updates the journey with the new signal and posts an interpretation. | Slack or Discord | | Analytics discovery | You want product-usage movement to feed discovery work. | Scheduled or analytics review | Reviews notable PostHog event movement and drafts candidate insights. | Slack or Discord | | Priority to delivery task | Prioritized work should move into execution with customer context intact. | Priority threshold or status change | Creates a delivery task and posts a team update. | Jira or Linear, with optional Slack or Discord update | | Quick wins to delivery task | High-impact, low-effort work should not go stale. | Impact and effort threshold | Creates a delivery task for the quick win and posts follow-up context. | Jira or Linear, with optional Slack or Discord update | | Merged pull request update | Shipping is happening faster than manual journey maintenance. | GitHub pull request merged | Uses PR context to update the journey and asks for validation where useful. | Slack or Discord | ## Destination differences Most template behavior stays the same when only the destination changes. | Destination type | Configure | Notes | | ----------------- | -------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | Slack | workspace integration, channel, message wording | Best when the team already reviews product work in Slack. | | Discord | workspace integration, channel, message wording | Best when product, support, or community discussions happen in Discord. | | Jira | workspace integration, project, issue type, title and description shape | Best when Jira is the delivery system of record. | | Linear | workspace integration, team, project or label, title and description shape | Best when Linear is the delivery system of record. | | GitHub | workspace integration, repository, branch or PR filters | Used as a trigger source for shipping-driven journey refreshes. | | PostHog or Stripe | connected source, event or measure, threshold or review cadence | Used when product or revenue movement should refresh journey context. | ## Good first templates Start with the smallest automation that closes a real gap: * **Weekly journey pulse** if the problem is visibility * **Priority to delivery task** if the problem is follow-through * **Merged pull request update** if the problem is journey drift after shipping * **Analytics signal change** if the problem is analytics staying disconnected from prioritization ## Setup checks Before activating a template: 1. Confirm the integration is connected. 2. Choose the narrowest journey or repository scope that will work. 3. Set the destination channel, project, repo, or team. 4. Review AI-written output instructions. 5. Save the draft. 6. Use **Run once** when the trigger is time-based and you want to inspect the result first. ## Common setup mistakes Start with one or two automations the team will actually notice. A smaller automation set is easier to validate, tune, and keep trusted. A draft is not useful until the channel, repo, team, or project is configured correctly. Finish routing before treating the template as ready. Automations amplify the underlying context. Clean up stale statuses, owners, and priorities before sending automated updates from them. ## Next step Read [Automations](/automations) for triggers, filters, actions, AI-assisted editing, run history, and activation behavior.