Skip to main content

Custom Events

Custom Events in GridStudio allow you to define and trigger your own event types within the platform, enabling advanced automation, integrations, and logic across your workflows. They are especially useful when standard event triggers (like "message received" or "form submitted") are not enough to capture your specific business processes.

Custom Events provide a powerful way to signal actions, pass data, and connect different components of your system—functions, flows, AI assistants, and external services.

Use Cases​

Advanced Workflow Triggering​

Trigger flows or functions based on events that are specific to your business, such as:

  • lead_qualified
  • invoice_overdue
  • shipment_delivered
  • support_escalated
  • payment_processed
  • task_assigned

Cross-System Communication​

Emit custom events from external systems (e.g., ERP, CRM, e-commerce platforms) to update GridStudio or vice versa:

  • Notify GridStudio when a customer makes a payment.
  • Trigger external webhooks when a custom event is fired.

AI Assistant Coordination​

Trigger custom events within AI assistants to orchestrate complex interactions:

  • After collecting user info, emit user_info_collected to start a verification flow.
  • Use consent_received to move to the next step in a multi-step bot.

Metrics and Monitoring​

Track specific actions by emitting custom events into your logging or analytics system:

  • Count how many times a user completes a task.
  • Monitor frequency of specific user behaviors.

Key Features​

Event Name & Payload​

Each custom event includes:

  • A unique name (e.g., user_subscribed, task_completed)
  • An optional payload (data object) that can be passed to downstream systems or flows.

Trigger Anywhere​

Custom events can be:

  • Triggered manually (via UI)
  • Triggered programmatically (from functions, flows, or API)
  • Triggered from external webhooks or applications
info

For more details on how to create custom events, see our SDK documentation page!