/hub/wmt-sports/build/workflows

Workflow Patterns

Common automation patterns built with Komo Workflows. Each pattern shows the trigger, actions, and how to set it up in the Komo Portal.

Pattern 1: Post-Event Follow-Up

After a user engages with a card at an event, send a follow-up email and add them to an "attended" list for future segmentation.

  • Trigger: Gameplay.DataCaptured -- Fires when a user submits a form within a card. Scope to specific event cards.
  • Action: ContactEmailSend -- Send a follow-up email with a post-event survey link and any prizes/content they unlocked.
  • Action: ContactAddToList -> "Event Attended" -- Add the contact to a list for future segmentation and reporting.
  • Action: ContactUpdate -> Add tag "event-attended" -- Tag the contact for cross-workflow filtering.

Pattern 2: Sponsor Lead Routing

When a qualified lead engages with a sponsor's card, check which sponsor it belongs to and route the lead data to that sponsor's webhook.

  • Trigger: Gameplay.DataCapturedQualified -- Fires when a qualified submission occurs (user meets entry criteria).
  • Decision: Check card name contains "Sponsor A" -- Branch based on which sponsor's card was played.
  • Action (Yes): HttpRequest -> POST to Sponsor A's webhook -- Send contact data, form fields, and gameplay results to the sponsor's endpoint.
  • Action: CompetitionEntryAddTags -> "sponsor-a" -- Tag the competition entry for per-sponsor reporting and export.
  • Action (No): HttpRequest -> POST to default/Sponsor B webhook -- Route to the next sponsor check or a default handler.

Pattern 3: Loyalty Points on Engagement

Award loyalty points when users complete a card, then check if they've crossed a tier threshold and upgrade their tier.

  • Trigger: Gameplay.Ended -- Fires when a user completes any card experience.
  • Action: LoyaltyAwardPoints -- Award loyalty points to the contact for completing the engagement.
  • Decision: Check if total points exceed tier threshold -- Evaluate whether the user has earned enough points for a tier upgrade.
  • Action (Yes): LoyaltyAddToTier + ContactEmailSend -- Upgrade the contact's loyalty tier and send a congratulations email.

Pattern 4: Receipt Validation Flow

When a receipt is successfully validated (purchase verification), issue a coupon and send a confirmation SMS.

  • Trigger: Gameplay.ReceiptValidationSuccess -- Fires when a user's uploaded receipt passes validation.
  • Action: ContactCouponIssue -- Issue a digital coupon or voucher to the validated contact.
  • Action: AssignBonusCompetitionEntries -- Grant bonus entries into the prize draw for the validated purchase.
  • Action: ContactSmsSend -- Send a confirmation SMS with coupon details and redemption instructions.

Available Triggers

Events that can start a workflow. Each can be scoped to a Workspace, Site, or individual Card.

Contact Triggers

  • Contact.Identified -- Contact identified
  • Contact.PropertyUpdated -- Contact property updated
  • Contact.Verified.Sso -- Contact verified by SSO
  • Contact.ListAdded -- Contact added to list

Gameplay Triggers

  • Gameplay.Started -- Gameplay started
  • Gameplay.Action -- Gameplay action occurred
  • Gameplay.Ended -- Gameplay ended
  • Gameplay.DataCaptured -- Data captured (incl. disqualified)
  • Gameplay.DataCapturedQualified -- Data captured (qualified only)
  • Gameplay.ReceiptValidationSuccess -- Receipt validated
  • Gameplay.ReceiptValidationRejected -- Receipt rejected
  • Gameplay.TreasureHuntCheckpointCompleted -- Treasure hunt checkpoint done
  • Gameplay.UploadApproved -- Upload file approved
  • Gameplay.UploadRejected -- Upload file rejected
  • Gameplay.LiveSurveyQuestionAsked -- Q&A question asked
  • Gameplay.LiveSurveyQuestionApproved -- Q&A question approved
  • Gameplay.LiveSurveyQuestionRejected -- Q&A question rejected

Prize Triggers

  • Prize.Awarded -- Prize awarded
  • Prize.ExtraDataCaptured -- Extra data form captured

Card Triggers

  • Card.CoverClicked -- Card cover clicked

Loyalty Triggers

  • Loyalty.PointsAwarded -- Points awarded
  • Loyalty.PointsRedeemed -- Points redeemed
  • Loyalty.TierAdded -- Tier added
  • Loyalty.TierRemoved -- Tier removed

Available Actions

Steps that a workflow can execute:

API, Utility & Flow

  • HttpRequest -- Call any external REST API
  • Decision -- Branch based on conditions
  • Split -- Split into multiple parallel branches

Contact

  • ContactFilter -- Filter contacts by properties
  • ContactUpdate -- Update contact properties
  • ContactAddToList -- Add contact to a list
  • ContactRemoveFromList -- Remove from list
  • ContactEmailSend -- Send email
  • ContactSmsSend -- Send SMS
  • ContactCouponIssue -- Issue a coupon
  • ContactVaultCardIssue -- Issue a vault card
  • AssignContactAchievement -- Award achievement

Competition & Gameplay

  • AssignBonusCompetitionEntries -- Grant bonus entries
  • CompetitionEntryAddTags -- Tag entries
  • CompetitionEntryRemoveTags -- Remove entry tags
  • GameplayFilter -- Filter gameplay events
  • AssignGameplayScore -- Assign a score

Loyalty

  • LoyaltyAwardPoints -- Award loyalty points
  • LoyaltyRedeemPoints -- Redeem points
  • LoyaltyAddToTier -- Add to loyalty tier
  • LoyaltyRemoveFromTier -- Remove from tier

Salesforce

  • SalesforceGetObject -- Query records
  • SalesforceCreateObject -- Create records
  • SalesforceUpdateObject -- Update records

Mailchimp

  • MailchimpUpsert -- Add or update subscriber
  • MailchimpUnsubscribe -- Unsubscribe
  • MailchimpDelete -- Delete subscriber
  • MailchimpAddTags -- Add tags
  • MailchimpRemoveTags -- Remove tags
  • MailchimpArchive -- Archive subscriber

Braze

  • BrazeTrackUser -- Track user event

Other

  • ContactThuziCheckIn -- Thuzi check-in

Building Workflows

Workflows are built visually in the Komo Portal under Automation > Workflows -- available at the Workspace, Site, or Card level. The drag-and-drop builder lets you:

  • Select a trigger event and scope it to specific cards, a site, or the entire workspace
  • Chain multiple actions in sequence
  • Add conditional branches with Decision nodes
  • Split into parallel execution paths
  • Map data between steps using dynamic field references
  • Test workflows before activating them

Full workflow reference: developers.komo.tech/workflows