Skip to navigation

Creating a Workflow with MoEngage

Creating a workflow using MoEngage as the trigger source allows you to process WhatsApp delivery tracking events and customer communication workflows directly from MoEngage integrations.

By configuring the MoEngage trigger inside Fyno, you can connect your WhatsApp delivery tracking URL, associate a preferred WhatsApp integration, and automate downstream workflows based on customer engagement or delivery events.

This setup helps centralize communication orchestration while ensuring that WhatsApp delivery updates and interaction flows are handled seamlessly across systems.

What is MoEngage Trigger?

The MoEngage trigger allows workflows to start based on delivery tracking events and engagement activities configured through MoEngage.

WhatsApp delivery tracking
Event-driven customer communication
Delivery status monitoring
Customer engagement workflows
Notification orchestration
Campaign response handling

A common use case would be:

1A WhatsApp notification is triggered from MoEngage.
2Delivery tracking updates are sent to Fyno.
3Fyno receives the delivery event.
4The workflow processes the event.
5Additional APIs, conditions, subflows, or user profile updates are executed based on delivery status or engagement data.

This helps businesses build centralized automation workflows around customer communication events.

Prerequisites

Before configuring a MoEngage trigger, ensure the following prerequisites are completed:

  • A valid MoEngage account is already configured externally.
  • Your WhatsApp integration is configured inside Fyno.
  • The delivery tracking URL is available from your MoEngage sender configuration.
  • Required APIs and webhook endpoints are already allowlisted if downstream API actions are involved.
  • You have clarity on the event payload structure MoEngage sends.
  • Your WhatsApp Business account is active and properly connected.

How to Configure a MoEngage Trigger

To configure a MoEngage trigger in Fyno, follow the below steps.

1

Create the workflow

Navigate to Workflows from the left navigation panel.

If you have already created workflows, you will see all the existing workflows in a card view. Click CREATE, enter a name and click SUBMIT. The Workflow canvas opens with the list of available triggers.

2

Select the MoEngage trigger

From the trigger selection canvas, select MOENGAGE. The MoEngage configuration panel opens. To pick a different trigger, click CHANGE TRIGGER.

3

Enter the delivery tracking URL

Under MoEngage Delivery Tracking URL, enter the delivery tracking URL from your MoEngage sender configuration in MoEngage Tracking URL.

https://api-0x.moengage.com/whatsapp/dlr/<vendor_name>

This URL allows MoEngage delivery tracking events to be routed correctly through the workflow.

4

Select the WhatsApp integration

Under Preferred WhatsApp Integration, select the WhatsApp integration that should be associated with this workflow.

This integration determines which WhatsApp Business Account will handle the communication flow.

5

Save

Click SAVE to save the workflow configuration.

Once saved successfully, the workflow becomes active and starts processing MoEngage delivery tracking events.

Trigger Settings Explained

The Delivery Tracking URL is one of the most important parts of the MoEngage trigger configuration. It acts as the endpoint through which delivery events are received and processed inside Fyno workflows.

Typical delivery events include:

  • Sent
  • Delivered
  • Read
  • Failed
  • Replied

These events can then be used to trigger additional workflow logic dynamically.

Why delivery tracking is important

Delivery tracking helps businesses:

  • Monitor message delivery performance
  • Detect failures automatically
  • Trigger fallback communication channels
  • Update customer engagement statuses
  • Create operational alerts
  • Build analytics and reporting workflows
If this happensThen
A WhatsApp message failsTrigger an SMS fallback
A message is deliveredUpdate the customer profile
A customer repliesInvoke a support workflow

How MoEngage Workflows Execute

Once the trigger is configured, the workflow behaves like a standard Fyno workflow. The MoEngage trigger acts as the workflow entry point, while the downstream nodes determine how the event should be processed.

After the trigger node, you can add the following:

API actions can be used to process delivery tracking events dynamically. Common examples include:

  • Updating CRM systems
  • Fetching customer details
  • Logging delivery statuses
  • Triggering support workflows
  • Syncing analytics systems
  • Updating campaign statuses

API configuration

1

Add the API action to the workflow canvas and connect it to the MoEngage trigger. The API configuration panel opens.

2

Under Allowlist URL, select the verified allowlisted endpoint that should be called. Only URLs added in the Allowlist section will appear here.

3

Select the HTTP Method, GET or POST. The selected method should align with your backend implementation.

4

Select the Content Type for the payload: None, JSON, Form Data, URL Encoded Form, XML or Text. JSON is commonly used for delivery event payload handling.

5

(Optional) Configure Headers if authentication or metadata is required.

Authorization: Bearer <token>
6

Configure the request payload using workflow variables and delivery event data.

{
"customer_id": "{{customer_id}}",
"delivery_status": "{{delivery_status}}",
"message_id": "{{message_id}}"
}

Example Workflow Scenarios

A common delivery retry workflow may behave as follows.

1MoEngage sends a delivery failure event to Fyno.
2The workflow checks the delivery status using a Condition block.
3If the message failed, an API block logs the failure into the CRM system.
4A fallback SMS workflow is triggered using a Subflow.
5The User Profile is updated with the latest delivery status.

Best Practices and Things to Know

  • Always validate delivery event payloads before workflow processing.
  • Use Conditions to handle retry and fallback logic properly.
  • Keep API calls optimized for high-frequency delivery events.
  • Use Subflows to modularize reusable communication logic.
  • Maintain meaningful variable naming conventions.
  • Test workflows thoroughly before enabling them in production.
  • Monitor workflow executions regularly to identify delivery anomalies.
  • Ensure the WhatsApp integration selected matches the MoEngage sender configuration.

How to raise Approval requests

If your workspace has Approval turned on, clicking GO LIVE creates an approval request instead of publishing the workflow right away. You can read more about it on the Approval Request page.