Action | Integration | Best for |
Slack Message | Slack | Real-time team alerts for notable customers |
Klaviyo Stream | Klaviyo | Pushing enriched data to all customer profiles |
Klaviyo Tag | Klaviyo | Triggering flows or building segments by tag |
Shopify Tag | Shopify | Tagging customers or orders for fulfillment or filtering |
Shopify Metafield | Shopify | Writing structured data to customer records |
Shopify Note | Shopify | Adding fulfillment instructions to orders |
Email Notification | Built-in | Notifying your internal team by email |
Webhook | Custom | Sending data to any external tool or endpoint |
HubSpot Contact | HubSpot | Putting OuterSignal data on HubSpot contacts |
Attentive Attribute | Attentive | Adding persona data to Attentive subscribers |
Postscript Subscriber | Postscript | Adding persona data to Postscript subscribers |
Omnisend Tag | Omnisend | Starting Omnisend automations by tag |
Omnisend Custom Property | Omnisend | Writing persona data to Omnisend contacts |
Gorgias Customer | Gorgias | Giving support agents context on who they're helping |
Gorgias Note | Gorgias | Leaving agents an internal note on a customer |
Gorgias Ticket | Gorgias | Queuing a support follow-up |
Superfiliate Enrollment | Superfiliate | Enrolling creators in your creator program |
Superfiliate Gifting | Superfiliate | Sending creators a gift |
Slack Message
Sends an alert to a Slack channel when a customer enters your segment. Best for VIP and high-signal customers where your team wants to act personally — reach out, send a gift, or escalate to a senior team member.
Configuration:
Trigger:
On Enter — fires once when a customer first matches the segment
Live Sync — fires on every matching order while the customer is in the segment
Channel — select the Slack channel to receive alerts (e.g. #alerts). The channel must exist in your Slack workspace first — create it in Slack, then refresh the channel list here
When to use On Enter vs Live Sync:
Use On Enter when you want a single alert the first time a notable customer appears — ideal for VIP notifications where you want to reach out once. Use Live Sync when you want your team alerted on every order from customers in this segment — useful for high-value repeat buyers where each order is actionable.
Klaviyo Stream
Pushes enriched OuterSignal data fields directly to Klaviyo customer profiles. This is the foundation of persona-based email — it makes demographic and enrichment data available in Klaviyo for segmentation, flows, and campaigns.
Configuration:
Trigger: Live Sync (always — streams update continuously)
Available fields — select which data to sync:
Age
Gender
Birth Date
Birth Year
Persona
Segment Name
At least one field must be selected. We recommend selecting all of them.
When to use: Set this up on your All Customers segment as the very first Playbook you create. It ensures every customer processed by OuterSignal gets their enriched data pushed to Klaviyo automatically — past and future.
Klaviyo Tag
Adds a tag to a customer's Klaviyo profile when they enter your segment. The tag can then be used to trigger Klaviyo flows, build Klaviyo segments, or organize customers by segment membership.
Configuration:
Trigger:
On Enter — fires once when a customer first matches the segment
Live Sync — fires on every matching order while the customer is in the segment
Tag Name — enter your tag using letters, numbers, hyphens, and underscores (max 50 characters). Examples: vip-customer, high-value, os-influencer, loyal-buyer
When to use: Use Klaviyo Tag for specific segments where you want to trigger a dedicated Klaviyo flow — for example, tagging all influencer customers to enroll them in an ambassador invite flow, or tagging a specific persona to trigger a persona-specific welcome sequence.
Shopify Tag
Adds a tag to a Shopify customer record or order when a customer enters your segment. Tags help you organize customers in Shopify, instruct your 3PL, or trigger Shopify-native automations.
Configuration:
Trigger:
On Enter — fires once when a customer first matches the segment
Live Sync — fires on every matching order while the customer is in the segment
Target Object:
Customer — tag is added to the customer record and persists across all future orders
Order — tag is added to the specific order associated with the customer
Customer Tag — enter your tag using letters, numbers, hyphens, underscores, and template variables (max 50 characters). You can use dynamic variables like os-{{segment_name}} to auto-populate with the segment name
Customer vs Order tagging:
Tag the customer when you want the tag to persist — for VIP status, persona labels, or any classification that applies to all their future orders. Tag the order when you need the instruction on a specific transaction — for example, to tell your 3PL to include a gift with this particular order.
📖 Shopify Tag Playbooks — Tagging, Metafields, and Order Notes (coming soon)
Shopify Metafield
Writes structured OuterSignal data to a custom metafield on the Shopify customer record. Metafields store richer, more structured data than tags — useful for powering your CS platform, storefront personalization, loyalty apps, or any Shopify-connected tool that reads metafields.
Configuration:
Target Object: Customer (metafields apply to the customer record)
Namespace — pre-set to outersignal — leave this as is. The full metafield identifier will be outersignal.your_key
Key — the name of the metafield (e.g. vip_status, biography, persona). Max 64 characters
Value — select the OuterSignal variable to write to this field (e.g. Biography, Persona). The value type shown (Single Line Text or Multi Line Text) is set automatically based on the field selected
Most common use: Writing a customer's OuterSignal biography to their Shopify record so it surfaces automatically in your CS platform (e.g. Gorgias, Kustomer) — giving your support team instant context on who they're talking to without leaving their helpdesk.
Shopify Note
Writes a free-text note to a Shopify customer or order record. Notes are visible in Shopify admin and to your 3PL — useful for fulfillment instructions, internal flags, or team context about why a customer is notable.
Configuration:
Trigger: On Enter or Live Sync
Target Object: Customer or Order
Note Template — free text up to 1,000 characters. Use dynamic variables to personalize the note e.g. VIP Alert: {{criteria_text}} — please include handwritten note and gift
Mode:
Append — adds your note to any existing notes (recommended — preserves history)
Overwrite — replaces existing notes completely (not recommended)
When to use: Shopify Note is ideal for 3PL fulfillment instructions that need to appear on the order itself — for example, flagging that a VIP customer should receive a handwritten note or premium packaging with every order.
Email Notification
Sends an internal email notification to a specified recipient when a customer enters your segment. This sends to your team — not to the customer.
Configuration:
Trigger: On Enter or Live Sync
Recipient Email — enter the email address that should receive the notification (e.g. [email protected])
When to use: A lighter-weight alternative to Slack alerts for teams that don't use Slack, or for routing specific segment notifications to a specific person (e.g. your wholesale team gets emailed when a retail buyer is detected).
Webhook
Sends a JSON payload to any HTTPS endpoint when a customer enters your segment. Connects OuterSignal to any external tool, CRM, or custom system that accepts webhooks.
Configuration:
Action Name — give your webhook a descriptive name
Trigger: On Enter or Live Sync
Webhook URL — the HTTPS endpoint to send data to. Must use HTTPS. POST is recommended — GET is not supported
HTTP Method — POST (default and recommended)
When to use: Webhooks are for advanced integrations — connecting OuterSignal to a CRM, a custom internal tool, or any platform not natively supported. If you're not sure whether you need a webhook, you probably don't — the native Klaviyo, Shopify, and Slack integrations cover most use cases.
HubSpot Contact
Creates or updates a HubSpot contact when a customer enters your segment, and writes OuterSignal data onto the contact properties your sales and marketing teams already use.
Configuration:
Trigger: On Enter or Live Sync
Identity property — fixed to email. Contacts are matched by email, and a new contact is created if none exists
Contact properties — map each HubSpot property name to a value or template variable (e.g. {{persona}}). At least one is required
When to use: When your team works out of HubSpot and wants persona and signal data on the contact record for lists, workflows, or sales follow-up.
Attentive Attribute
Sets custom attributes on an Attentive subscriber when a customer enters your segment, so you can build Attentive segments and journeys around who your customers are.
Configuration:
Trigger: On Enter or Live Sync
Identify subscriber by — Phone or Email. The one you pick is used when available, and the other is the fallback. Never both
Custom attributes — map each attribute name to a value or template variable (e.g. {{persona}})
Set different attributes on exit (optional) — turn this on to set a different set of attributes when a customer leaves the segment. Leave it off to use the same attributes on entry and exit
When to use: When you run SMS or email in Attentive and want to target messages by persona or segment.
Postscript Subscriber
Updates custom properties on an existing Postscript subscriber when a customer enters your segment.
Configuration:
Trigger: On Enter or Live Sync
Update mode:
Patch — merges these properties into the subscriber (recommended)
Put — replaces the properties OuterSignal manages
Named properties — pick the customer fields to sync as Postscript properties
Custom property — map anything not in the named list to a property name of your own
When to use: When you run SMS in Postscript and want to segment subscribers by persona or other OuterSignal data.
Omnisend Tag
Adds a tag to an Omnisend contact when a customer enters your segment. You can use the tag to start Omnisend automations or build segments.
Configuration:
Trigger: On Enter only
Tag — the tag to add (e.g. vip-customer). Required
When to use: When you want a segment to kick off a specific Omnisend automation. To write data onto the contact instead, use Omnisend Custom Property.
Omnisend Custom Property
Sets custom properties on an existing Omnisend contact when a customer enters your segment.
Configuration:
Trigger: On Enter or Live Sync
Custom properties — map each Omnisend property name (e.g. outersignal_persona) to a value or template variable (e.g. {{persona}})
The contact is matched by email and only updated. If the customer isn't in Omnisend yet, they're skipped
When to use: When you want persona and signal data available on Omnisend contacts for segmentation and personalization.
Gorgias Customer
Creates or updates the customer in Gorgias and fills in their customer fields with OuterSignal data, so agents can see who they're talking to right inside a ticket.
Configuration:
Trigger: On Enter only
Fields — choose which OuterSignal value goes into each Gorgias customer field: Biography, Customer Name, Email, Customer Persona, Segment Name, Customer Age, Customer Gender, or follower count. Biography is set up for you
When to use: Set this up on your All Customers segment if your support team uses Gorgias, so every customer's biography is there when they write in.
Gorgias Note
Adds an internal note to the customer's Gorgias record when they enter your segment. Only your agents can see it, never the customer.
Configuration:
Trigger: On Enter only
Note title (optional) — e.g. OuterSignal: {{segment.name}}
Note text — required. Use template variables to personalize it, e.g. High-value shopper — {{persona}}, {{order_count}} orders
When to use: When you want agents to know something specific about a customer, like their VIP status, the next time they're in touch.
Gorgias Ticket
Opens an internal Gorgias ticket when a customer enters your segment, so your support team has a follow-up waiting in their queue. The customer never sees it.
Configuration:
Trigger: On Enter only
Ticket subject — required, e.g. Follow up: {{segment.name}}
Ticket message — e.g. Reach out to {{first_name}} — {{persona}}, {{order_count}} orders
When to use: When your support team should personally reach out to customers in a segment, for example new VIPs.
Superfiliate Enrollment
Adds the customer to Superfiliate by email and enrolls them in the creator program you choose. Their Instagram and TikTok handles go along when we have them.
Configuration:
Trigger: On Enter only. Superfiliate can't remove a creator from a program, so there's no exit or Live Sync option
Program — choose one of your active Superfiliate programs. If none show up, create or reopen a program in Superfiliate, then refresh
Good to know:
If the customer is already in Superfiliate, we update their name. Their code and link stay the same
A creator can be in one program at a time. Customers already in another program stay there
If Superfiliate can't verify an Instagram or TikTok handle, we still enroll the customer by email, without the handle
When to use: Pair it with a segment of the creators and influencers among your customers to invite them into your creator program.
Superfiliate Gifting
Adds the customer to Superfiliate by email and enrolls them in the gifting campaign you choose. Each gift ships a real product, and Superfiliate can't take one back.
Configuration:
Trigger: On Enter only. Superfiliate can't take a gift back, so there's no exit or Live Sync option
Gifting campaign — choose one of your active Superfiliate gifting campaigns. Each one shows whether it's automatic or manual and who ships it
Before you turn it on:
Automatic campaigns can ship with no further step. Manual campaigns wait for the creator to claim the gift
Set a quantity cap on the campaign in Superfiliate. It's the only limit on how many gifts this action can send
Pausing the playbook doesn't stop gifts that are already queued. To stop them, archive the campaign in Superfiliate
When to use: When you want to send product to the creators among your customers, for example new customers with a large following.
Choosing the right action
Not sure which action to use? Here's a quick decision guide:
I want my team to know immediately when a VIP orders → Slack Message (On Enter)
I want enriched data in Klaviyo for all customers → Klaviyo Stream (All Customers segment)
I want to trigger a specific Klaviyo flow for a segment → Klaviyo Tag
I want to tag customers in Shopify for VIP status → Shopify Tag (Customer, On Enter)
I want to flag each VIP order for my 3PL → Shopify Tag (Order, Live Sync) or Shopify Note
I want OuterSignal data in my CS platform → Shopify Metafield (Biography)
I want to notify a team member by email → Email Notification
I want to connect OuterSignal to a custom tool → Webhook
I want OuterSignal data on HubSpot contacts → HubSpot Contact
I want persona data in my SMS platform → Attentive Attribute or Postscript Subscriber
I want to start an Omnisend automation for a segment → Omnisend Tag
I want persona data on my Omnisend contacts → Omnisend Custom Property
I want my support agents in Gorgias to know who they're talking to → Gorgias Customer (Biography)
I want my support team to follow up with a customer → Gorgias Ticket
I want to invite creators into my creator program → Superfiliate Enrollment
I want to send creators a gift → Superfiliate Gifting
📖 Deep Dive: Creating and Configuring a Playbook (coming soon)