Skip to main content

​
Event Studio

Event Studio is where you define what counts as an Event. Every meaningful action — a message arriving, a contact field changing, an automation firing — can be captured as an Event, inspected with full context, and used to trigger the right follow-up.

Event Studio

Define and track meaningful activity. Know what happened and when.

Automations

Turn Studio Events into actions. Start workflows automatically.

​
Overview

Think of Event Studio as the workspace’s memory. Unlike a chat message (customer-facing) or a Note (human comment), an Event is a system-level fact created in Studio that is searchable, filterable, and usable in automation. Use Event Studio when you need to:
  • Decide which activities should create an Event (and which should stay as plain logs)
  • See what happened, to whom, and with what context — with contact and conversation linked
  • Trigger automations and Contact → Pipeline moves directly from Events
Event Studio defines the what and when. Automations define the what next.

​
What you can create in Event Studio

An Event in Studio is a structured record: something happened, to whom, when, and with what context. Studio lets you work with Event types such as:
  • Inbound message received (WhatsApp, Instagram, Web Chat)
  • Outbound message sent / delivered / read / failed
  • New conversation started or resolved / archived
  • Contact created, updated, or assigned
  • Custom field value collected (e.g., city = Mumbai via an ask node or WhatsApp Flow)
  • Label added or removed
  • Automation started, completed, or paused
  • Support ticket created or status changed
  • Webhook received from an external system
You choose which of these become first-class Events in your workspace. Not every tiny interaction needs to be an Event — Studio should record activity that matters to tracking, reporting, or triggering the next step.

​
How Event Studio connects

Event Studio is a standalone Studio for defining and recording activity. It is not where you manage internal human context or business stages:
  • For internal human context, use Notes inside Inbox — e.g., “Customer prefers evening callbacks.”
  • For business progress and stage tracking, use Pipelines — e.g., Lead → Qualified → Won
  • For the actual chat with the customer, use Conversations in Inbox
Within Studio itself:
  • Every Event is associated with a contact (and often a conversation), so you can open a contact and see its Studio event history in chronological order.
  • Studio Events are the most common automation triggers. When a matching Event occurs, the automation runs.
  • A Studio Event can also trigger a pipeline move via Contact → Pipeline — Studio records the activity, Pipelines track the business outcome separately.

​
Where to find Event Studio

1

Open your workspace

Choose the correct channel context from Workspace → Channels if your workspace uses multiple channels. Event Studio is scoped to the active workspace/channel.
2

Go to Event Studio

Navigate to Workspace → Event Studio in the sidebar (labeled Events in some workspaces). If you don’t see it, your workspace may surface events through the Contact profile or Conversation timeline instead — check the Activity or History tab inside a contact or conversation.
3

Search or filter

Use search and filters to narrow by contact, event type, time range, or source.
The fastest way to see Events for one person is to open the contact in Contacts or open the conversation in Inbox — SkyFree shows that contact’s recent Studio Events alongside messages and Notes.

​
What you can do in Event Studio

​
View event history

See a reverse-chronological list of Studio Events for the workspace or for a single contact. Each entry shows when it happened and what triggered it.

​
Inspect event details

Open an Event to review:
  • Timestamp — when the activity occurred (workspace timezone)
  • Contact — who the Event is about (name, phone, contact ID)
  • Source — where it came from (e.g., whatsapp, web-chat, automation, api, webhook, system)
  • Event type / name — a short identifier such as message.received or contact.updated
  • Properties / context — structured data carried by the Event (e.g., message text snippet, field name and new value, automation name, campaign ID)
  • Related records — links to the conversation, automation run, or pipeline record if applicable
The exact fields you see depend on the Event type. A message.received Event carries different properties than a contact.label_added Event.
Typical Studio filters include:
  • Event type — e.g., messages, contact updates, automation events
  • Source / channel — WhatsApp, Instagram, Web Chat, API
  • Contact — phone number, name, or contact ID
  • Date range — Today, 7 days, 30 days, or custom range
  • Automation or pipeline — filter to Events tied to a specific workflow
Use filters before searching on large workspaces — it’s much faster than scanning the full history.

​
Use Studio Events in automation

Studio Events are the primary way to start automations without manual action:
  1. Create or edit an automation in Automation → Create a Workflow.
  2. Choose an Event Studio trigger such as Inbound message, New conversation, or Webhook event.
  3. Build the downstream logic (reply, assign, update field, run Contact → Pipeline).
  4. Publish and monitor execution — each run is itself traceable as Studio Events.
Learn more in Select a Trigger and Create a Workflow.

​
Event lifecycle in Studio

  1. Activity happens — a customer sends a message, a field is updated, or a system job completes.
  2. Studio records an Event with timestamp, contact, source, and properties based on your Studio definition.
  3. Context is stored so the Event is searchable and can be inspected later.
  4. Something acts on it — either an automation whose trigger matches the Studio Event, or a teammate reviewing history and taking manual action (reply, add Note, move Pipeline stage).
If no automation matches, the Event still remains in Studio history for reporting and debugging.

​
When to use Event Studio

Use Event Studio when you need a reliable, filterable trace of activity that can drive automation:
  • You need to know what happened, to whom, and when — e.g., message.received at 17:02 from +91… with campaign ID → Event Studio
  • You need to trigger a workflow automatically when that activity occurs → configure a Studio Event as an automation trigger
For other jobs, use the dedicated feature instead of Studio:
  • Leave internal handoff context for the next shift — “Customer asked to be called after 5 PM.” → Notes
  • Track where a contact is in your sales or support process → move from New → Qualified → Pipelines
  • Talk to the customer directly → Conversations in Inbox

​
Best practices in Event Studio

  • Name and classify Studio Events consistently. If your workspace creates custom Events via API or webhooks, use a stable naming pattern (e.g., payment.completed, demo.booked) so triggers don’t miss them.
  • Filter before you search. On busy workspaces, start with event type + date range, then add the contact filter.
  • Pair Studio Events with a Pipeline or Note where a human needs context. A Studio Event says what happened; a Note explains what to do about it.
  • Test Studio Event-triggered automations with real data. Send a controlled test message and confirm the Studio Event appears before marking the automation live. See Manage Live Flows.
  • Use Studio for debugging. If an automation didn’t fire, check Studio first whether the expected Event was recorded at all — the trigger is usually the first place to look.
Last modified on August 28, 2026