Workflow Actions

Actions are the building blocks of your workflows - they define what happens after your trigger fires. Chain actions together to create powerful automations that save time and deliver personalized experiences.

How Actions Work

Actions are executed in sequence, with each action receiving data from previous steps. Use connection paths to handle success and failure scenarios.

Trigger: Data captured (Including disqualified)
├── Action 1: Filter (validates data)
│   ├── Success Path → Action 2: Send email
│   └── Failure Path → Action 3: Add to list ("Incomplete Data")

Quick Action Finder

Use the step labels shown in the workflow builder. Code identifiers are included for reference.

I Want To…	Step label	Code identifier	Category
Send an email	Send email	`ContactEmailSend`	Contacts
Update user profile	Update	`ContactUpdate`	Contacts
Add to a list	Add to list	`ContactAddToList`	Contact Lists
Award loyalty points	Award points	`LoyaltyAwardPoints`	Loyalty
Create a Salesforce record	Create object	`SalesforceCreateObject`	Salesforce
Filter on contact data	Filter	`ContactFilter`	Contacts
Branch with conditions	Split (decision)	`Decision`	Shared
Send a LocalCard gift	Send LocalCard from template	`LocalCardSendCardFromTemplate`	Cards and Coupons
Issue a LocalCard campaign gift	Generate LocalCard campaign gift	`LocalCardGenerateCampaignGift`	Cards and Coupons
Send an HTTP request	Send HTTP request	`HttpRequest`	Shared
Run custom JavaScript	Custom code	`CustomCode`	Shared
Add a competition entry	Add entry	`AddCompetitionEntry`	Competition Entries

Contact Actions

Manage contact data, communications, and list memberships.

Data Management

Step label	Code identifier	Purpose	Example Use
Update	`ContactUpdate`	Modify contact properties	Update preferences, scores, tags
Filter	`ContactFilter`	Apply conditional logic	Route users based on properties
Add to list	`ContactAddToList`	Add contact to list	Segment users for campaigns
Remove from list	`ContactRemoveFromList`	Remove from list	Unsubscribe or re-segment

Communications

Step label	Code identifier	Purpose	Example Use
Send email	`ContactEmailSend`	Send personalized email	Welcome emails, notifications
Send SMS	`ContactSmsSend`	Send SMS message	Urgent alerts, mobile campaigns

Rewards & Recognition

Step label	Code identifier	Purpose	Example Use
Issue coupon	`ContactCouponIssue`	Issue one or more coupons	Reward completions, bulk incentives
Award achievement	`AssignContactAchievement`	Award achievement badge	Recognize milestones, gamify
Issue Vault card	`ContactVaultCardIssue`	Issue digital wallet card	Membership cards, tickets
Issue Vii card	`ViiCardCreateAndLoad`	Create and load a Vii digital gift card. See Vii Gift Cards	Gift card prizes

Issue coupon configuration

The Issue coupon step supports issuing multiple coupons in a single workflow step.

Setting	Description	Default
Offer	The coupon offer to issue from (offers in the workflow’s hub)	Required
Issued coupon URL(s) / Issued coupon code(s)	Workflow variables to save the coupon link and/or code into (create them with Manage variables). At least one is required	—
Limit per contact (Advanced)	Maximum coupons per contact from this offer. `0` or empty means unlimited	No limit
Quantity (Advanced)	Number of coupons to issue (supports variables, e.g. `{{variables.count}}`)	1
Allow partial award (Advanced)	When Quantity is more than 1, issues as many as are available instead of following Offer limits exceeded	Disabled

Use the mapped variable in later steps, for example {{variables.coupon_link}} in a Send email or Send SMS step. For a step-by-step example, see Issue a coupon to everyone who submits a form. Output Variables: When issuing a single coupon:

coupon_id - The issued coupon ID
coupon_link - Direct link to the coupon
coupon_code - The coupon barcode/code

When issuing multiple coupons:

coupon_id - JSON array of coupon IDs
coupon_link - JSON array of coupon links
coupon_code - JSON array of coupon codes
coupon_count - Total number of coupons issued

Output Paths:

Success - Coupons issued successfully
OfferLimitsExceeded - Contact or offer limits prevent issuing, or unique codes have run out
OfferExpired - Coupon offer is outside its availability window

Example: Issue Multiple Coupons

Trigger: Data captured (Including disqualified)
├── Issue coupon:
│   ├── Offer: "10% Discount"
│   ├── Quantity: 3
│   ├── Contact Limit: 5
│   ├── Allow Partial Award: true
│   ├── Success Path → Send email (include coupon_count in message)
│   └── OfferLimitsExceeded Path → Send email (limit notification)

Specialized Integrations

Action	Purpose	Required Data	Example Use
ContactThuziCheckIn	Thuzi platform check-in	Event details	Event attendance tracking

LocalCard Gift Cards

Send digital gift cards to contacts through the LocalCard integration. Requires a LocalCard connected app. See LocalCard Gift Cards for setup.

Step label	Code identifier	Purpose	Example Use
Send LocalCard from template	`LocalCardSendCardFromTemplate`	Send a gift card from a template	Reward winners, incentivize participation
Generate LocalCard campaign gift	`LocalCardGenerateCampaignGift`	Issue a gift from an existing campaign	Bulk gift distribution, promotional campaigns

Send LocalCard from template configuration:

Field	Description	Required
Card template ID	The LocalCard card template to use	Yes
Card value	Dollar value of the gift card (supports dynamic values)	Yes
Delivery method	How the card is delivered: `Email`, `Sms`, or `Link` (default: Email)	No
Recipient message	Personalized message for the recipient (supports dynamic values)	No
Communication message	Notification message sent with the card	No
Deliver at	Schedule delivery for a future date/time	No
On behalf of	LocalCard managed account ID (`acct_…`) to issue from instead of the API key’s account (supports dynamic values)	No

Generate LocalCard campaign gift configuration:

Field	Description	Required
Campaign ID	The LocalCard campaign to issue from	Yes
Gift value	Dollar value of the gift (supports dynamic values)	Yes
Delivery method	How the gift is delivered: `Email`, `Sms`, or `Link` (default: Link)	No
Recipient message	Personalized message for the recipient (supports dynamic values)	No
On behalf of	LocalCard managed account ID (`acct_…`) to issue from instead of the API key’s account (supports dynamic values)	No

Example: Gift card reward workflow

Trigger: Prize.Awarded
├── ContactFilter: Prize type = "Gift Card"
│   ├── Success: LocalCardSendCardFromTemplate
│   │   ├── Card template: "Reward Gift Card"
│   │   ├── Card value: $25
│   │   └── Delivery: Email
│   └── Failure: ContactEmailSend → "Standard prize notification"

Both LocalCard actions require a LocalCard connected app. Go to Company Settings → Connected Apps and connect your LocalCard account with your API key before using these actions.

Integration Actions

Connect with external platforms and services.

Salesforce CRM

Action	Purpose	Required Data	Example Use
SalesforceCreateObject	Create new CRM record	Object type, field mappings	Add leads, opportunities, contacts
SalesforceUpdateObject	Update existing record	Object ID, field updates	Update lead status, add notes
SalesforceGetObject	Retrieve CRM data	Object ID or search criteria	Validate existing records, get context

Example: Lead to CRM Flow

Trigger: Gameplay.DataCapturedQualified
├── SalesforceCreateObject: Create Lead
│   ├── Success: ContactUpdate → Tag "CRM Synced"
│   └── Failure: Add to "CRM Sync Failed" list
└── ContactEmailSend: Confirmation to sales team

Mailchimp Email Marketing

Action	Purpose	Required Data	Example Use
MailchimpUpsert	Add/update subscriber	Email, list ID	Sync contacts to email campaigns
MailchimpAddTags	Apply subscriber tags	Tag names	Segment for targeted campaigns
MailchimpRemoveTags	Remove subscriber tags	Tag names	Update segmentation
MailchimpUnsubscribe	Unsubscribe contact	Email address	Honor unsubscribe requests
MailchimpArchive	Archive subscriber	Email address	Clean inactive subscribers
MailchimpDelete	Permanently delete	Email address	GDPR compliance, data removal

Example: Email List Sync

Trigger: Contact.ListAdded ("Newsletter Subscribers")
├── MailchimpUpsert: Add to Mailchimp list
├── MailchimpAddTags: ["Komo User", "Newsletter"]
└── ContactUpdate: Mark "mailchimp_synced" = true

Braze Customer Engagement

Action	Purpose	Required Data	Example Use
BrazeTrackUser	Send user event to Braze	Event name, properties	Trigger Braze campaigns, analytics

Competition Entries Actions

Actions specific to competition entries.

Action	Purpose	Required Data	Example Use
AddCompetitionEntry	Add a contact as an entry into another competition card, from a competition entry or a completed survey	Target card	Share entries between linked competitions, turn survey submissions into entries
AssignBonusCompetitionEntries	Grant extra entries	Entry count (supports Liquid variables)	Reward engagement, boost participation
CompetitionEntryAddTags	Tag competition entries	Tag names	Categorize entries, track sources
CompetitionEntryRemoveTags	Remove entry tags	Tag names	Clean up categorization

Gameplay Actions

Actions in the Gameplay step group for filtering and scoring gameplay events.

Action	Purpose	Required Data	Example Use
GameplayFilter	Filter gameplay events	Filter conditions	Route based on scores, completion
AssignGameplayScore	Set custom scores	Score value, context	Custom scoring beyond default

AddCompetitionEntry configuration

Use this step to enter a contact into a separate competition card from the one that triggered the workflow. Useful for grand-prize draws, cross-promotion, or aggregating entries from multiple competitions into a single pool. Add entry is available after competition entry triggers (such as Data captured (Including disqualified) and Data captured (Qualified entries only)) and after the Survey Completed trigger. After Survey Completed, it turns the survey submission into a competition entry on the target card, such as a Form card. The workflow must be scoped to a hub. If it isn’t, or the trigger isn’t supported, the step shows an Invalid Scope or Invalid Trigger warning.

Workflow with an Execute on Survey Completed trigger connected to an Add entry step that shows its target card

Setting	Description	Required
Target card	The competition card to add the entry to. Must be a card that has competition enabled and is not the same card the workflow is scoped to. Cards with gameplay (such as games and quizzes) are not selectable.	Yes

How fields are copied: fields are matched by their Unique ID. Each field in the source entry or survey submission is copied to the target card’s form field with the same Unique ID. Fields with no match on the target form are skipped. The step fails, and no entry is created, if:

A required field on the target card’s form has no matching source field.
A matching field has a different field type on the source and the target.
A selected option doesn’t exist on the target card’s matching field. Options are matched by their value.
The target card is the card that the source entry came from.

After Survey Completed, only Add entry is available from the Competition Entries steps. AssignBonusCompetitionEntries, CompetitionEntryAddTags and CompetitionEntryRemoveTags still need a competition entry trigger.

Example: Engagement Bonus System

Trigger: Gameplay.Action (social share)
├── AssignBonusCompetitionEntries: +3 entries
├── CompetitionEntryAddTags: ["Social Sharer"]
└── LoyaltyAwardPoints: 50 points

AssignBonusCompetitionEntries accepts either a fixed number or a Liquid variable (for example, {{ contact.fields.entry_bonus }}) for the entry count. Fractional values are truncated to a whole number when the workflow runs. This action is available on the Gameplay.DataCaptured, Gameplay.ReceiptValidationRejected, and Gameplay.ReceiptValidationSuccess triggers.

Loyalty Actions

Manage loyalty programs, points, and tier memberships.

Step label	Code identifier	Purpose	Example Use
Award points	`LoyaltyAwardPoints`	Credit points to account	Reward actions, milestone bonuses
Redeem points	`LoyaltyRedeemPoints`	Deduct points for redemption	Process point spending
Add to tier	`LoyaltyAddToTier`	Promote to higher tier	Recognize high-value users
Remove from tier	`LoyaltyRemoveFromTier`	Demote from tier	Handle tier downgrades

Example: Tier Progression System

Trigger: Loyalty.PointsAwarded
├── ContactFilter: Total points >= 1000
│   ├── Success: LoyaltyAddToTier ("Gold")
│   └── ContactUpdate: Next tier progress
└── ContactEmailSend: Points confirmation

Shared & Flow Actions

Control workflow logic and external communication.

Flow Control

Step label	Purpose	Required Data	Example Use
Split (decision)	Branch workflow logic	Decision conditions	If/then logic, A/B routing
Split (%)	Route contacts by percentage	Split percentages	A/B style routing

There is no delay or wait step type in workflows.

Join paths after a split

Branching does not have to stay separate forever. After Split (decision) or Split (%), you can connect multiple paths into one later step so shared follow-up actions run once for every branch.

Trigger: Custom code (set points_to_award)
├── Split (decision): points_to_award >= 5000
│   ├── Big Spender → Award achievement ("Big Spender") → Award points
│   └── Fallback → Award points

In the builder, drag a second connection onto a step that already has an input. An extra input handle appears while you drag so you can complete the join. See Join (converge) paths for screenshots, loop rules, and auto layout notes.

External Communication

Step label	Code identifier	Purpose	Example Use
Send HTTP request	`HttpRequest`	Send HTTP request	Custom webhooks, API calls

Custom Code

Run JavaScript inline as part of a workflow when you need transformation, calculation, or conditional logic that the built-in steps don’t cover.

Step label	Code identifier	Purpose	Example Use
Custom code	`CustomCode`	Execute JavaScript against workflow variables	Transform values, derive new fields, format strings

How it works:

The script runs in a sandboxed JavaScript environment.
Workflow variables are available as inputs to the script.
Define one or more outputs with the data types you’ll return; the values you assign to those outputs become available to downstream steps.

Custom Code steps run in a restricted sandbox and do not have access to the network, file system, or third-party libraries. For HTTP calls, use the HttpRequest step instead.

Example: Custom Webhook Integration

Trigger: Prize.Awarded
├── HttpRequest: POST to fulfillment API
│   ├── Success: ContactUpdate → "fulfillment_requested"
│   └── Failure: Add to "Fulfillment Failed" list
└── ContactEmailSend: Winner notification

Action Best Practices

✅ Design for Success and Failure

Always handle both success and failure paths:

Action: SalesforceCreateObject
├── Success Path: 
│   ├── ContactUpdate: Tag "CRM Synced"
│   └── ContactEmailSend: Confirmation
└── Failure Path:
    ├── Add to "CRM Failed" list
    └── HttpRequest: Alert IT team

✅ Use Descriptive Names

Name your actions clearly for easy maintenance:

❌ ContactEmailSend: "Email Template 1"
✅ ContactEmailSend: "Welcome Email - New User Onboarding"

✅ Validate Data Before Actions

Use filters to ensure data quality:

Trigger: Data Captured
├── ContactFilter: Email format is valid
│   ├── Success: ContactEmailSend
│   └── Failure: Add to "Invalid Email" list

Chain related actions for efficiency:

New Member Workflow:
├── ContactUpdate: Set member_status = "active"
├── ContactAddToList: "Active Members"
├── LoyaltyAwardPoints: 100 welcome points
└── ContactEmailSend: Welcome package

Advanced Action Patterns

1. Progressive Data Collection

Build profiles over multiple interactions:

Trigger: Data Captured
├── ContactFilter: Profile completeness < 50%
│   ├── Success: ContactEmailSend ("Complete Your Profile")
│   └── ContactUpdate: profile_complete_date = now()

2. Smart List Management

Automatically manage list memberships:

Trigger: Loyalty.PointsAwarded
├── ContactFilter: Total points >= 500
│   ├── Success: 
│   │   ├── ContactAddToList: "VIP Members"
│   │   └── ContactRemoveFromList: "Standard Members"

3. Multi-Channel Notifications

Send notifications across multiple channels:

High-Value Prize Workflow:
├── Split (decision): Prize value > $50
│   ├── Success:
│   │   ├── Send email (detailed email)
│   │   └── Send SMS (urgent SMS)
│   └── Fallback:
│       └── Send email (standard notification)

Troubleshooting Actions

Common Issues

Problem	Likely Cause	Solution
Action fails silently	Missing required data	Add data validation before action
Integration timeouts	External API is slow	Add error handling, increase timeout
Duplicate actions	Action runs multiple times	Check for duplicate triggers; workflows cannot contain loops
Wrong data passed	Previous action failed	Verify success/failure paths
Cannot save — loop	A connection creates a cycle	Remove the looping connector; the editor shows `Workflows can not have loops` or `Workflow contains a loop`

Testing Actions

Test with real data - Use actual contact records and scenarios
Verify external integrations - Confirm data arrives in target systems
Check error handling - Intentionally break integrations to test failure paths
Monitor execution time - Ensure actions complete within reasonable timeframes

Performance Tips

Optimize Action Chains

Use the right Split - Split (decision) branches on conditions; Split (%) divides contacts by percentage. Neither runs branches in parallel
Early filtering - Place filters early to avoid unnecessary actions
Batch operations - Group similar actions when possible

External Integration Efficiency

Cache responses - Store API responses to avoid duplicate calls
Use webhooks - Let external systems push data instead of polling
Implement retries - Handle temporary failures with retry logic

What’s Next?

Monitoring guide → - Track action performance and troubleshoot issues
Workflow triggers → - Explore triggers to pair with these actions
Back to workflows guide → - Return to main workflows documentation

Need help implementing a specific action? Contact support at [email protected]

Workflow Actions

How Actions Work

Quick Action Finder

Contact Actions

Data Management

Communications

Rewards & Recognition

Issue coupon configuration

Specialized Integrations

LocalCard Gift Cards

Integration Actions

Salesforce CRM

Mailchimp Email Marketing

Braze Customer Engagement

Competition Entries Actions

Gameplay Actions

AddCompetitionEntry configuration

Loyalty Actions

Shared & Flow Actions

Flow Control

Join paths after a split

External Communication

Custom Code

Action Best Practices

✅ Design for Success and Failure

✅ Use Descriptive Names

✅ Validate Data Before Actions

✅ Group Related Actions

Advanced Action Patterns

1. Progressive Data Collection

2. Smart List Management

3. Multi-Channel Notifications

Troubleshooting Actions

Common Issues

Testing Actions

Performance Tips

Optimize Action Chains

External Integration Efficiency

What’s Next?