CRM & API Integration

Komo's Workflow engine lets you set up triggers based on user actions and automatically push data to external systems. Many popular services have built-in connected apps — for everything else, you can make custom HTTP requests to any API.

How It Works

Every Komo integration follows the same pattern: a trigger fires, then one or more actions execute. You configure this in the Komo Portal under Automation > Workflows — no code required for built-in integrations. 

Trigger                          Action(s)
─────────────────────    ──►    ─────────────────────
User submits form                Salesforce: Create Lead
User wins prize                  Mailchimp: Tag Subscriber
Coupon redeemed                  HTTP Request: POST to your API
Gameplay ended                   Braze: Track User

Available Triggers

These are the events that can kick off a workflow. You can scope any trigger to a specific card, site, or the entire workspace.

Gameplay.DataCaptured

User submits a form within a card. Contains all form field values.

Gameplay.DataCapturedQualified

Qualified submission — user meets eligibility criteria you've defined.

Gameplay.Ended

Card experience finished. Contains gameplay results and score.

Prize.Won

User won a prize. Contains prize details and winner info.

Coupon.Redeemed

Digital coupon was redeemed. Contains coupon and contact data.

Contact.Created

New contact created in Komo. Useful as a catch-all sync trigger.

Built-in Connected Apps

These platforms have native integrations in Komo — select them as workflow actions and map fields directly in the UI. No HTTP configuration, no code.

Salesforce

  • Get Object — query existing records
  • Create Object — create Leads, Contacts, etc.
  • Update Object — update existing records

Mailchimp

  • Upsert Subscriber — add or update list members
  • Tag Subscriber — apply tags for segmentation

Braze

  • Track User — update user profiles and attributes

Tip: Built-in apps handle authentication, retry logic, and field mapping for you. Always use a connected app when one exists for your service — it's faster and more reliable than a custom HTTP request.

Custom HTTP Requests (Any API)

For services without a built-in connector — HubSpot, Zoho, Klaviyo, your own backend, or any REST API — use the HTTP Request action. It can call any URL with custom method, headers, body, and authentication. 

// Example: Push a lead to HubSpot via HTTP Request action
Method: POST
URL: https://api.hubspot.com/crm/v3/objects/contacts
Headers:
  Authorization: Bearer YOUR_HUBSPOT_TOKEN
  Content-Type: application/json
Body:
{
  "properties": {
    "email": "{{ contact.email }}",
    "firstname": "{{ contact.first_name }}",
    "lastname": "{{ contact.last_name }}",
    "lead_source": "Komo - {{ card.name }}",
    "komo_score": "{{ gameplay.score }}",
  }
}

The {{ field.name }} placeholders are template variables — Komo replaces them with real values from the trigger event when the workflow runs.

This covers any integration need. If a service has a REST API, you can connect Komo to it. Common examples: push leads to HubSpot, send events to Segment, update records in Airtable, trigger Slack notifications, call your own microservice.

Webhooks (Server-Side Event Stream)

For scenarios where you need your own backend to receive and process events — complex business logic, multi-destination routing, data enrichment — Komo can also send webhook POST requests directly to your endpoint.

Site Events

Site published, unpublished

Prize Events

Prize won, claimed, draw completed

Form Events

Form submitted, data captured, qualified

Card & Coupon Events

Gameplay started/ended, coupon issued/redeemed

Configure webhook URLs in the Komo Portal under Settings > Webhooks. Your endpoint receives a JSON POST for each event, which you can then transform and route however you need.

Choosing the Right Approach

Approach Best for Setup
Built-in App Salesforce, Mailchimp, Braze — standard sync No-code, 5 minutes
HTTP Request Any REST API — HubSpot, Klaviyo, Airtable, custom No-code, 10-15 minutes
Webhooks Complex logic, enrichment, multi-destination routing Requires your own backend

You can use all three simultaneously. For example: built-in Salesforce sync for leads, an HTTP Request to Slack for notifications, and webhooks to your analytics pipeline.

Field Mapping

When configuring any action, you map Komo data to the destination's fields. Here's an example for a Salesforce Lead:

Komo Field Destination Field
contact.email Email
contact.first_name FirstName
contact.last_name LastName
form_fields.company Company
card.name LeadSource

Workflow Patterns

More patterns — post-event follow-ups, lead routing, loyalty points, and more.

Webhook Event Reference

Full payload schemas for all webhook event types.