Creating an Action

Step-by-step instructions for spinning up a new Action—via template, guided wizard, or from-scratch build—so you can choose the fastest path for your workflow.

Overview

Creating an Action is flexible by design—you can grab a ready-made template, sketch a custom flow visually in Composer, or define every step manually from scratch.

Which method is right for you?

Method
Use when…
Ideal for…

A common workflow already exists and you need it live in under a minute.

New builders, non-technical teammates, anyone prioritizing speed over granular tweaks.

You want to drag-and-drop steps, add branches, and see the flow visually before publishing.

Product/Ops leads, PMs—anyone who prefers a no-code, WYSIWYG experience.

The workflow is novel or complex and no template fits; you need full control over every trigger, condition, and action.

Power users, engineers, automation pros who aren’t afraid of detail.

TLDR: Pick Template for speed, Composer for drag-and-drop control, or Scratch for total customization.

Look below at how to create an action if you're wondering...

  • Where do I find and customize a template

  • How do I build an Action entirely from scratch?

  • What’s the Composer and why should I use it?

  • How do I add multiple actions to the same trigger?

  • Why isn’t my Action saving or publishing?


✏️ Creating an Action

1

Go to the Actions page for your Delphi.

2

Either choose a Template, click New Flow to Create From Scratch, or start typing in the Composer.

Delphi Templates

  1. Browse the pre-built templates section and select one based on either their brief descriptions or the detailed template guides below. Each template can be customized to your needs.

Available Templates

User Engagement and Retention

  • Inactivity nudge: Messages inactive users to re-engage them.

  • Weekly progress check: Sends a weekly check-in message.

  • Conversation Recap: Auto-sends a summary every 50 messages.

Follow-ups and Reminders

  • User-requested reminder: Follows up when users ask for a reminder.

  • Event reminder: Reminds users about upcoming events.

  • Follow-up message: Reconnects with users about past topics or mentioned events.

  • Post-conversation plan: Sends next steps to users after a conversation.

  • Instant meeting setup: Auto-sends your calendar link upon request by users.

  • Pre-event pep talk: Calls users an hour before events with a pep talk.

Messsage Scripting

  • Thank you message: Sends a welcome message to new users.

  • Support response: Provides a predefined reply to support requests.

  • Feedback collection: Requests feedback after a user’s first conversation.

Data Collection

  • User tagging: Categorizes users based on their interactions.

  • Data forwarding: Forwards user data to an API.

  • User properties: Stores a user’s location when mentioned.

Conversion & Growth

  • Personal contact: Notifies you about highly inactive users.

  • Convert Users: Sends users a signup link after 10 chat messages.

  • Quota Reached: Offers a discount when users hit their chat quota limit the first time.

Multi-Step Actions

  • Member Check-In - Part 1: Enables accountability for members only, 2 part process.

  • Member Check-In - Part 2: Enables accountability for members only, 2 part process.

  • Birthday Wishes: Sends a personalized note on every user’s birthday.

  1. Customize your selected template’s settings. Take a look at the Triggers and Actions Guides for a detailed explanation of how to customize each trigger and action.

  2. Click “Save” in the top right corner. Now you’ve published your first Action!


Scratch

  1. Click the “New Flow” box in the “Start from Scratch” section.

  2. Click "Add Trigger"

  3. Click the “When: User ends a conversation” box under “Trigger” to customize your trigger.

  4. In the right-side popup, select your desired trigger type from the dropdown list. Go to the Triggers Guide to find all available triggers with details on how they work, customization options, and best use cases, or see below for a short version of all triggers available.

Triggers (events that start a flow)
  • Alert Triggered: An alert activates.

  • Conversation Ended: A user finishes a conversation.

  • Usage: A user reaches a set number of messages or voice/video minutes.

  • Quota Reached: A user hits their message or minute quota.

  • Inactivity: A user remains inactive for a set period.

  • Phone Number Captured: A user provides their phone number.

  • Product Recommended: Your Delphi suggests a product.

  • Membership: A user purchases a specific membership tier.

  • Payment Made: A user completes a payment.

  • On a Specific Date/Time: The scheduled date and time arrives.

  • On a Recurring Schedule: The defined schedule repeats.

  1. Complete your trigger setup with two final choices: user tags (optional) and frequency. See the Triggers Guide for information on these too.

  2. Click “Add Action.”

  3. Click the “Do: Notify the user with a Prompt via Medium” box under “Action” to customize your action.

  4. In the right-side popup, select your desired action type from the dropdown list. Go to the Actions Guide to find all available actions, with descriptions of how each one works and its specific configuration settings.

  5. Complete your action setup by selecting when to execute the action after the trigger. See the Actions Guide for information on this too.

  6. To add multiple actions for the same trigger, click the “Add Action” button in the top left corner. This allows you to create a second and third action, each of which can be customized independently while still being triggered by the same event.

  7. Review any validation warnings or errors that appear in the top-left corner. Address these before proceeding.

  8. Click “Save” to publish your flow. The status indicator will change from “Unsaved” (yellow) to “Published” (blue) when complete.


Composer

  1. Use the Composer to quickly describe the Actions flow you want—no need to build it step by step. Simply type what you want your Delphi to do, and it will automatically generate the flow for you, including up to 3 actions if your request is clear. See below for a full list of triggers and actions you can request.

The Composer works best for triggers specific to the Actions feature, such as conversation ended, user inactivity, quota reached, usage milestone, phone number captured, payment made, a specific date/time, or a recurring schedule.

Triggers (events that start a flow)
  • Alert Triggered: An alert activates.

  • Conversation Ended: A user finishes a conversation.

  • Usage: A user reaches a set number of messages or voice/video minutes.

  • Quota Reached: A user hits their message or minute quota.

  • Inactivity: A user remains inactive for a set period.

  • Phone Number Captured: A user provides their phone number.

  • Product Recommended: Your Delphi suggests a product.

  • Membership: A user purchases a specific membership tier.

  • Payment Made: A user completes a payment.

  • On a Specific Date/Time: The scheduled date and time arrives.

  • On a Recurring Schedule: The defined schedule repeats.

Actions (what happens in response)
  • Send Message: Contact Owner: We send you a message.

  • Send Message: Contact User: Your Delphi sends your user a message.

  • Update Tag: Assigns/removes a tag from the user.

  • Update Property: Assigns/removes a property from the user.

  • Custom API: Sends data to an external API.

  1. Once the flow is generated, you can edit it in two ways:

    1. Use the sidebar: Modify your trigger and action settings just as described in Option B.

    2. Edit directly in the Composer: Modify your prompt in the box at the bottom of the page to fine-tune your Delphi’s behavior.

Last updated