Actions Guide
Actions are the “do” step of every automation flow—the tasks Delphi executes once a trigger fires.
Overview
Whether you’re sending a message, tagging a user, or calling an external API, Actions turn trigger events into outcomes. Below is a short list of available actions, followed by detailed guidance.
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.
Send Message: Contact Owner
This action allows Delphi (the company) to send you, the Delphi owner, personalized updates or reminders based on specific user interactions. Instead of generic notifications, Delphi crafts tailored messages using context from the trigger event to ensure every response is relevant.
Customize It: Select your preferred notification type from the Notification Type dropdown. Options include:
Email – Delphi will send you a context-aware notification via email.
Text Message – Delphi will send you a personalized notification via SMS.
In the box labeled “Describe what should be sent, using the data selected above,” enter a general instruction rather than a specific scripted message. Delphi will generate the right response dynamically, using real-time context from the trigger event. Example:
If your trigger is set for new membership purchases and you want Delphi to send you an email reminder to welcome them, you might enter: “Remind me to greet new members and acknowledge their subscription.”
We will then generate a situationally appropriate message, such as: “You have a new member, [Name]. They signed up for [Membership Tier] on [Date]. You might want to send them a welcome message and share next steps!”
Example:
If you set the Send Message: Contact Owner action to trigger when a new user subscribes to a membership, you might enter: “Remind me to greet new members and acknowledge their subscription.”
Delphi will then generate a context-aware notification, such as: “You have a new member, [Name]. They signed up for [Membership Tier] on [Date]. You might want to send them a welcome message and share next steps!”
This ensures you stay updated on important interactions and can respond promptly.
Use It: Stay informed about important user interactions while ensuring that every notification is highly relevant and tailored to the situation. Get alerts for quota limits, payments, or membership sign-ups, and ensure your responses are timely, thoughtful, and specific.
Send Message: Contact User
This action allows your Delphi to contact a user with a response that is personalized in real-time based on the instructions you provide. Instead of a fixed, scripted message, Delphi dynamically generates a reply using the provided guidance and context from the conversation.
Customize It:
Select your preferred notification type in the Notification Type dropdown. The available options depend on:
The type of trigger you selected
When the action is scheduled relative to the trigger event (For a deeper explanation of the three timing options, see point 9 below).
Choose the preferred response method:
Reply in Conversation – Your Delphi will immediately respond in any active medium (chat, voice call, video call, SMS conversation, phone call) with a reply that follows your specified guidance. This response will replace whatever Delphi would have otherwise generated while still maintaining contextual relevance. If you pick a medium from one of the options below, it will send a separate message via that medium.
Email – Your Delphi will send the user a personalized email crafted using your instructions. A “Click Here to Respond” button at the bottom will direct them to your Delphi web interface, allowing them to continue the conversation seamlessly.
Text Message – Your Delphi will send a personalized response via SMS. The user can then continue chatting with Delphi over text, ensuring a fluid and ongoing interaction.
Phone Call – Your Delphi will call the user and read aloud a tailored response based on your instructions. The user can then continue speaking with Delphi on the phone, making the conversation feel more natural and interactive.
In the “Describe what should be sent, using the data selected above” box, provide general instructions rather than a specific message. This ensures Delphi adapts the response based on the user’s situation.
Example:
If you set the Send Message: Contact User action to trigger when a user reaches their message quota, you might enter: “Let them know they’ve hit their limit and offer an upgrade option.”
Delphi will then generate a response such as: “Hey [Name], you’ve reached your message limit for this plan. If you’d like to continue the conversation, you can upgrade your access [here]. Let me know if you have any questions!”
This ensures the user receives a timely and relevant notification, encouraging them to take the next step.
Use It: Ensure users receive prompt, personalized, and relevant responses that keep conversations flowing naturally and intelligently. Delphi doesn’t just reply—it continues the interaction, maintaining context and engagement.
Update Tag
This action allows you to either add or remove a tag from a user based on their interaction. Tags help you segment users, personalize engagement, and track behavior effectively.
Customize It:
Toggle between “Add Tag” or “Remove Tag” to specify whether you want to apply or remove a tag.
Select the applicable tag from the “Properties” dropdown.
Example 1: If a user expresses interest in a premium feature, you can select “Add Tag” and apply a “Potential Upsell” tag. This allows you to later target these users with special offers or tailored messages.
Example 2: If a user upgrades from a trial to a paid membership, you can select “Remove Tag” to remove the “Trial User” tag. This ensures they no longer receive trial-specific content and helps maintain accurate user segmentation.
Use It: Segment users dynamically, trigger personalized follow-ups, and refine user categorization based on their latest interactions.
Note*: Once you create a tag, you can no longer delete the tag itself, but you can remove the tag from a user.
Update Property
This action allows you to either set or remove a property from a user based on their interaction. Properties store key details about users, such as preferences, activity levels, or status, enabling more personalized experiences and targeted engagement.
Customize It:
Toggle between “Set Property” or “Remove Property” to specify whether you want to assign or delete a property.
Select the applicable property from the “Properties: Property to set” dropdown.
Example 1: If a user completes an onboarding tutorial, you can select “Set Property” and assign “Onboarding Completed = Yes.” This allows you to track which users have finished onboarding and tailor future interactions accordingly.
Example 2: If a user cancels their subscription, you can select “Remove Property” and delete “Active Subscriber.” This ensures they no longer receive member-specific content or perks.
Use It: Store valuable user attributes, track key milestones, and refine audience segmentation to create more relevant and meaningful interactions
Custom API
Understand It: This action sends a POST request to a specified API with user details, including name, email, phone number, timestamp, and the triggered event.
Customize It: 1) Specify the endpoint URL in the “Endpoint URL” box. 2) Configure headers under “Headers.” We automatically create the Content-Type header with the value application/json. You can add one additional header, such as an API token for authorization. Any API token you enter will be encrypted for security and automatically decrypted when sent with the request, ensuring the receiving system can validate that the data is coming from Delphi.
Example: If a user completes a purchase, Delphi can send their name, email, and purchase details to your CRM or analytics tool, ensuring seamless data tracking across platforms.
Use It: Sync user attributes with external systems, update CRMs, or integrate with analytics tools.
When should the action run? (timing)
Choose when to execute the action after its trigger:
Immediate
Fires as soon as the trigger occurs. Example — After a recommendation, message the user instantly: “I think you’d love [Product]. Here’s a link: [link].”
Fixed Delay
Waits for a set time relative to the trigger (minutes/hours/days). Example — 2‑hour follow‑up after a cart add: “Still thinking about [Product]? Your cart is waiting!”
Custom Delay
Let Delphi determine the best time based on context or your instruction (describe briefly). Example — “Send the user a message on their birthday.” Delphi checks the stored birthdate and sends: “Happy Birthday, [Name]!”
Last updated