AI creates the first journey. Automations keep it up to date.AI creates the first journey.
Automations keep it up to date.

AI Assistant

Custory’s AI assistant helps you make sense of customer friction, organize scattered evidence, and turn journey insights into clearer next steps.

Because it works inside your actual journey, it can see the steps, personas, insights, metrics, and connected product context behind the problem. That makes it useful for real product work — not just generic brainstorming.

Use it to draft journey structure, identify where customers get stuck, clarify which friction points deserve action, or turn an insight into a concrete fix.

The same assistant can work from Custory, Slack, Discord, or MCP-compatible tools, so your team can use the journey context wherever the work is happening.

Reads from: Journey steps, personas, insights, metrics, evidence, and connected product signals.

Helps you: Clarify customer problems, organize evidence, draft solutions, and move from insight to follow-up work.

Works in: Custory, Slack, Discord, and MCP-compatible tools.

Team member

Invite the AI into your workflow by @mentioning it in comments, asking it to review a step, or drafting together. All edits and updates stay visible and attached to the journey so you keep full control and transparency.

The AI works best when it participates in the work that is already happening. You can use it inside Custory to refine wording, synthesize evidence, or clean up a step. In Slack or Discord, @mention it to get context-aware answers or turn a conversation into structured follow-up work.

Bring it in with: @Custory in comments, step reviews, Slack threads, or Discord discussions

It works from: The current item, surrounding journey context, attached evidence, and conversation history

All changes stay: Visible and linked to the journey objects they affect—so your team stays in control

Automations

Set recurring or event-driven automations that keep the journey current without manual upkeep. If data changes, a threshold is hit, or a review comes due, Custory can update the journey or kick off the next action automatically.

This is where the AI layer becomes operational leverage. Instead of using AI only for one-off help, teams can let it maintain parts of the customer understanding loop for them: refreshing metrics, posting updates to Slack, drafting linked work, or surfacing the next issue that deserves attention.

Runs from: Recurring schedules, source updates, thresholds, and workflow events

Can do: Update the journey, create items, notify owners, or launch follow-up actions

Best outcome: Metrics, insights, and priorities stay fresh without the team babysitting the system

Common flows

Automations

Custory automations help teams keep the journey current without constant manual upkeep. They watch for changes on a schedule or from connected systems, then update journey context, create follow-up work, or send the right update to the team so customer understanding keeps moving with the product.

The core loop is simple: a signal comes in, Custory interprets it in journey context, and the system either updates the map, creates the next action, or notifies the right people. That makes automations useful for the work product teams already do every week: keeping metrics fresh, spotting new friction, and turning changes into visible follow-up.

Because the automation system is built around Custory objects, the output stays useful inside the product rather than becoming another disconnected alert stream. The result is less maintenance work and a journey system that stays much closer to reality.

Starts from: A schedule, a product signal, a GitHub event, or a change inside Custory

Can do: Update journey context, create follow-up work, refresh priorities, or send team updates

Why teams use it: To keep customer understanding current without adding more manual process

Set Up with AI

Describe the outcome you want in plain language and Custory drafts the automation around it. A product lead can say “pull weekly PostHog funnel data, update the onboarding journey, and flag new drop-off risk” and start from a strong first draft inside the editor, then fine-tune the workflow visually before turning it on.

This is how Custory treats AI: as a faster way to get from intent to a usable workflow. The draft maps your goal into concrete triggers, actions, connected integrations, and journey updates, then hands everything back to the editor so the team can inspect, adjust, and approve the final version with confidence.

That is especially valuable for lean teams that want the leverage of automation without becoming automation specialists. AI removes the blank page, while the editor keeps the workflow readable, flexible, and fully under the team’s control.

Input: A plain-language goal such as pulling analytics, posting updates, or creating new journey insights

Output: A drafted automation with trigger logic, actions, and the right journey scope already mapped

Why it matters: Teams get to a high-quality workflow faster, then refine it in the editor instead of starting from zero

Templates

Templates give teams a fast, opinionated starting point for recurring Custory workflows. Instead of starting from scratch, you can begin with patterns designed to keep journeys current, surface high-signal customer changes, and route the right follow-up into the rest of your stack.

The strongest templates are not just generic automations. They are pre-shaped around the way Custory works: structured journey context in the middle, connected signals on one side, and execution or team updates on the other. That makes them especially useful for teams who want fast setup without losing the logic of why the workflow exists.

Examples: Weekly journey pulse, PostHog event drift updates, active team member recaps, and priority handoff flows

Editable: Yes, teams can change triggers, actions, AI-drafted text, integrations, and scope

Why it matters: The team gets to a useful Custory workflow quickly without rebuilding the same operating logic every time

Triggers

Automations in Custory can run on a schedule or react to events, which means the journey can stay current without manual policing. You can review metrics every Monday morning, react when an item crosses a priority threshold, or listen for GitHub pull requests opening or merging.

This is where the product moves from static system to current system. Time-based triggers handle recurring monitoring and reporting. Event-based triggers react when something actually changes, so updates land when they are relevant instead of after someone remembers to follow up.

That helps teams catch friction, quality issues, and priority shifts earlier. Instead of waiting for a weekly meeting to notice that onboarding dropped, a PR merged, or an item’s impact changed, the system can move first and bring the right context with it.

Schedule: Hourly, daily, or weekly runs for recurring reporting, monitoring, and updates

Event: Custory item events and GitHub events such as item updates, threshold changes, PR opened, and PR merged

Why it matters: The journey stays current because important changes can trigger action automatically, not only on review day

Integrations

Connected integrations turn automations into real operating workflows instead of internal reminders. An automation can read product signal from PostHog, create or update a journey insight in Custory, notify the team in Slack, and open follow-up work in GitHub or another connected system as one continuous flow.

Signals can come in from the tools your team already uses, and the output can land exactly where the next decision or action should happen. Custory keeps the journey in the middle, so the workflow feels connected instead of improvised.

Instead of pushing generic notifications around the stack, teams can create workflows that refresh journey context, send focused updates, and open follow-up work while keeping the original customer problem visible.

Analytics: PostHog and Stripe as connected signal sources for behavior and revenue context

Execution: GitHub and connected work systems for follow-up actions and product delivery loops

Communication: Slack and Discord for alerts, summaries, and keeping the team aligned in-channel

Why it matters: Workflows can read from one system, update Custory, and push the next action outward without losing context

How does Custory AI help the team move faster?

AI helps in two ways: it builds your first journey draft from your product material so you start with context, not a blank canvas. But more importantly, automations turn AI into operational leverage—they keep the journey current automatically, pull signals from your stack, and kick off follow-up work without manual policing. That is where you see the biggest speed increase: less manual upkeep, more captured signals, faster prioritization.

What can automations actually do?

Automations can pull data from analytics or billing tools, create journey items on the right step where the problem actually lives, open issues in issue tracking or code systems, and send Slack messages — all from a single workflow triggered on a schedule or by an event. The power is that the signal, the decision, and the execution all stay connected.

What data sources can automations read from?

PostHog for event volume, funnel data, and user behavior. Stripe for payment failures, refunds, and subscription activity. GitHub for PR and deployment events. More sources are being added continuously.

Can I use the AI from Slack without opening the app?

Yes. Connect the Custory bot to Slack or Discord and @mention it in any channel or thread. It uses the same context and tool access as the in-app assistant, so you can ask questions, create items, and trigger updates without leaving the conversation.

How does the MCP server work with coding tools?

Connect Custory as an MCP server inside Claude, Cursor, or any compatible AI environment. The agent can then read your journey, inspect items, and create or update records as part of implementation workflows — keeping the journey in sync with what gets shipped.

Do I need to build automations from scratch?

No. Custory includes purpose-built presets for common scenarios like funnel drops, payment failure spikes, and Slack summary digests. You pick a trigger, configure the data source and actions, and the automation handles the rest.