Skip to content
Migrated — not yet rewrittenCarried over from the previous help center on 28 August 2026. Content is accurate as published but has not been rewritten to the current article template.

Call Flows Release

NEW FEATURE RELEASE: Call Flows & Webhook Integrations

Section titled “NEW FEATURE RELEASE: Call Flows & Webhook Integrations”

Location: Call Flows, Webhooks
​Release Date: 12/12/25


This release introduces Call Flows and a complete Webhook Integration framework (incoming and outgoing). Together, these capabilities give customers more control over how calls are executed and how data moves into and out of MojaAI. The release adds new configuration surfaces in the portal, new execution options for campaigns, and persistent call-level metadata through custom tags.


As call workflows become more complex, customers need greater flexibility than static campaign logic alone can provide.

This release enables customers to:

  • Reuse call execution logic across campaigns through Call Flows

  • Integrate MojaAI with CRMs and internal systems via webhooks

  • Enrich calls with external context using custom tags

  • Receive structured call events for automation and reporting

This is a foundational release that unlocks future capabilities rather than solving a single isolated use case.


  • Call Flows — reusable call execution logic with visual builder

  • Incoming Webhooks — send data into MojaAI from external systems

  • Outgoing Webhooks — send call events out of MojaAI

  • Custom Tags — configurable data enrichment for call logs

  • New Portal Sections for configuration and monitoring


  1. Call execution — A campaign determines whether to execute using a Routing Plan (existing) or a Call Flow (new).

  2. Data coming in — External systems send data to MojaAI using Incoming Webhooks. Incoming data is evaluated against configured Custom Tags so the platform can interpret and enhance call data.

  3. Data going out — As events occur, MojaAI sends Outgoing Webhooks to configured destinations based on selected event types.

  4. Persistence — Custom Tags are stored with call logs and remain available after call completion.


What Is a Call Flow?

A Call Flow defines reusable logic that controls how a call runs. Campaigns can now explicitly choose how calls are executed. Each campaign can use Routing Plans (existing default behavior) or Call Flows (new execution option).

How Call Flows Work

  1. A Call Flow is created using the visual builder

  2. One or more campaigns reference that Call Flow

  3. When a call runs, MojaAI executes the Call Flow logic

  4. If a campaign does not select a Call Flow, existing behavior is unchanged

The call flow builder processes each node and routes the call accordingly based on logic defined in the flow.

What Incoming Webhooks Do

Incoming Webhooks allow external systems to send structured data into MojaAI. Common use cases include:

  • CRM or lead data enrichment

  • Qualification or intent signals

  • External classification results

How Incoming Webhooks Work

  1. An Incoming Webhook configuration is created in the portal

  2. MojaAI generates a webhook URL with an organization-specific key

  3. External systems POST data to that URL (e.g., https://domain/call-data?key=ABC)

  4. MojaAI evaluates the payload against configured Custom Tags

  5. Matching tag values are associated with the call and persist after completion

What Outgoing Webhooks Do

Outgoing Webhooks are event-driven notifications sent to external systems when specific actions or state changes occur inside MojaAI.

How Outgoing Webhooks Work

When configuring an outgoing webhook, customers select which event types should trigger webhook deliveries. Event types include call lifecycle events (call started, call completed), tag-related events, and other execution events.

What Are Custom Tags?

Custom Tags are user-defined key/value pairs that enrich call data. They are stored securely and can be populated from multiple sources:

  • Incoming Webhooks

  • DNI (Dynamic Number Insertion)

  • Inbound RTB

  • Call Flow tag nodes

Why Tags Matter

Custom Tags enable:

  • Post-call reporting and analytics

  • CRM synchronization

  • Downstream automation

  • Call segmentation

Tags are persisted per call, scoped to the organization, and accessible via API using the call log ID.


  1. Navigate to Data → Call Flows

  2. Click Create Call Flow

  3. Use the visual builder to define nodes and logic

  4. Save the Call Flow

  5. Edit a campaign and set Execution Mode to Call Flow

  6. Select the desired Call Flow and save

  1. Navigate to Data → Webhooks → Incoming Webhooks

  2. Create an Incoming Webhook configuration

  3. Copy the generated webhook URL

  4. Configure your external system to send POST requests to the URL

  5. (Optional) Define Custom Tags to control how inbound data is evaluated and stored

  1. Navigate to Data → Webhooks → Outgoing Webhooks

  2. Create an Outgoing Webhook configuration

  3. Enter the destination URL

  4. Select event types to trigger notifications

  5. Save and activate


  • Call Flows → Data → Call Flows

  • Incoming Webhooks → Data → Webhooks → Incoming Webhooks

  • Outgoing Webhooks → Data → Webhooks → Outgoing Webhooks

  • Custom Tags → Data → Webhooks → Custom Tags

  • Webhook Monitoring → Data → Webhooks → Incoming/Outgoing Webhook Requests

  • Campaign Configuration → Campaigns → [Select Campaign] → Execution Settings


  • Existing campaigns continue to function unchanged

  • Routing Plans remain the default execution mode

  • Call Flows and Webhooks are opt-in

  • No migration is required