Mailmodo 0ff833fb

Mailmodo Support

Stay updated on the status of all your company's support tickets.

Raise a Ticket here

Customer portal

trigger will allow you to trigger the journey to specific contacts in a list, segment, or uploaded through a CSV that you will enroll manually. This is best for lead nurturing, webinar registration, and so on. 

Imagine you're hosting a webinar and have a list of contacts who have previously shown interest in your webinars or related content. With this trigger, you can set up an automation journey specifically for these contacts

You should have organized your contacts into lists or segments within Mailmodo. This ensures that you can easily select the group of contacts you want to target with this trigger.

: Create a new journey and click on "Start from scratch".

 Select 'Manual Enrolment’ as the trigger. 

Design the complete journey and click on the Next button. 

You can review all the important details of the journey at one glance, such as the list selected, nodes used, testing the journey, and so on to see if they match your requirements perfectly. 

Once you have reviewed the journey, click on the "Publish Now" button.

In this case, when the trigger is a manual trigger for specific contacts, the journey would wait for the user to add contacts in the journey to run the journey for them. 

Whereas in cases of automated triggers like ‘contact added to a list, change in property of a contact, occurrence of an event etc’ the journey would automatically wait for the trigger event to happen and run the journey for the respective contacts. 

 Go to the actions tab to open the pop-up to get the enroll contacts button.

 Click on ‘Enroll contacts’ to add contacts to the journey. 

Select lists or Upload a CSV file to set the journey running for contacts.

Trigger journeys for specific contacts by manually enrolling them

 trigger will allow the contact that is added to the list selected, to enter the journey. We will allow you to either create or choose from the existing lists that you have created on Mailmodo. This is best for welcome emails, onboarding campaigns, and so on. 

If you operate an e-commerce website and want to greet new customers with a warm welcome and useful information, this trigger is your solution. It automatically initiates a welcome email series whenever a new customer joins the "New Customers" list. This series can express gratitude, introduce products, and provide exclusive offers or recommendations.

You should have organized your contacts into lists within Mailmodo.

 Select from the existing lists from the dropdown or create a new one by clicking on the "Create a new list" button

 Click on the checkbox to enroll existing contacts on the list into the journey. 

This means that the journey will work for all the existing contacts, including those you'll add in the future. It checks and runs based on the current date and time.

 Design the complete journey and click on the 

 Once you have reviewed the journey, click on the "Publish Now" button

The journey being published would mean that the journey is running for the existing contacts if selected and is waiting for the new contacts to get added to the list. 

If you have any queries then reach out to us at 

Trigger journey when a contact is added to a list

trigger allows you to trigger the journey when there is a change in the value of a contact’s property to a new value. This is best for personalized marketing, upgrade plan series, etc.

Imagine you offer different subscription plans for your software, and you want to provide an exceptional experience for customers who upgrade to a higher-tier plan.  You can automatically start a journey whenever a contact changes their "Billing Plan" from a lower-tier plan to a higher one. 

You must have defined contact properties, that you want to monitor for changes. 

 Select ‘Change in property of a contact’ as the trigger and click on "Configure trigger"

 Select the contact property from the dropdown. 

For example - If the Property name is Billing Plan then the selected property should be ‘Billing Plan’ 

If you don’t want to set the exact value of the change, select ‘is any value’ in the operator and it will set the journey running for change in the contact’s property to anything. 

 if you want to trigger the journey for change in contact property of any contact, or select a particular list or a static segment if you want to trigger the journey to change in contact property to only the contacts belonging to them

 Design the complete journey and click on the 

You can review all the important details of the journey at one glance, such as the contact property selected, nodes used, testing the journey, and so on to see if they match your requirements perfectly.

 Once you have reviewed the journey, click the 

 button. The journey being published would mean that the journey is running and is waiting for the new contacts whose property value would change. 

: Definition of various options available

If you have any queries, then reach out to us at 

Trigger journey when there’s a change in contact property

Trigger journey when there is a change in contact property

 trigger will allow a contact to enter a journey based on their activity recorded on your website, app, or other platforms. To send events in Mailmodo, use our event API or integration with the Segment App. 

When contacts engage with specific content, such as downloading an ebook or viewing a video, this trigger can start content engagement journeys with related resources, follow-ups, and calls to action.

Ensure you capture events related to your customer's activities on your website/store. To learn more about custom events on mailmodo, 

: Go to the Journey section in Mailmodo app and click Create Journey button.

 Select ‘Occurrence of an event’ as the trigger. 

 Search and select the relevant event from the dropdown. 

. You can add a filter to set up a trigger for a specific event property. 

 You will be prompted to map the personalization parameters added in the template or subject line in the send campaign block to contact properties or attributes of the custom event selected in the trigger block. 

You can also map these parameters to properties that have additional details in them. These are called "

". In the example below, the "user_details" property is a nested object under the event "Onboarding Completed".

You can also capture an event that has a property containing a list of recipients or products in it. These are called "

". You can map the parameters to the individual items in the list. 

 To split the journey further, you can add the "Custom event condition" block and direct the contacts to different paths in the journey based on the properties of the event that they correspond to.

You can learn more about the custom event condition block 

 Design the complete journey and click on the "Next" button

When you click on the "test journey" button on the Review and Publish page, you will see the test data in JSON format. You can tweak the values in this test data according to your requirements.
Please make sure to enter the correct values for which you want the journey to be triggered.

 Click on the Publish button once the journey is ready. The journey being published would mean that the journey is running and is waiting for the event to occur and run the journey for that contact.  

Trigger journeys on occurrence of an event

 trigger allows you to trigger a journey when a contact submits a response to the form used in an email template sent to them. This is best for collecting feedback, customer engagement, survey research, etc.

When a contact submits a contact or inquiry form embedded in an email template, you can use this trigger to initiate an automated lead nurturing journey. This journey can include a thank-you email, follow-up responses, and information tailored to the contact's inquiry.

You must create email templates with embedded forms using Mailmodo's features.

 Select ‘Form submission’ as the trigger. 

 In the right panel, click on Select the template button to select the template having the desired form or forms. 

. Select the desired form in the dropdown. 

In case you want to run journeys based on submissions, click on the save button to complete the configuration. 

Or if you want to trigger the journey when a specific question is submitted, click on the trigger on a specific submission option to create rules for form questions.

You will be prompted to map the form fields ( form selected in the trigger block) to personalization parameters in your send campaign block. 

For instance consider this flow, a. Trigger block --> b. send campaign block.

If there are personalization parameters in your template and subject line, you will be asked to map those parameters with the form attributes of the trigger block. This can be helpful when you wish to trigger a campaign based on form submission and personalize the content of your campaign depending on user input.

To split the journey further, you can add the "Form submission condition" block and direct the contacts to different paths in the journey based on the responses that they give to questions in the form.

When you click on the "test journey" button on the Review and Publish page, you will be prompted to enter test data for the form that is in the selected template.
Please make sure to enter the correct data in the input field for which you want the journey to be triggered.

 Design the complete journey and click on the "Next" button. 

You can review all the important details of the journey at one glance, such as the template selected, nodes used, testing the journey, and so on to see if they match your requirements perfectly.

 Once you have reviewed the journey, click on the Publish button. The journey being published would mean that the journey is running and is waiting for the new contacts whose property value would change. 

Trigger journey on form submission

Here's a guide to trigger journeys in Mailmodo using an API.

For setting up a journey through an API trigger:

Create a journey using API / Webhook as a trigger point. 

Then on the journey page, click on 'Enroll Contacts' as shown below. 

Use the API endpoint to start this journey.

 https://api.mailmodo.com/hooks/start/<journeyid> (this will be used to trigger the particular journey every time a user-defined action occurs)

 Api key can be obtained from API Keys tab in Settings

curl --location --request POST'https://api.mailmodo.com/hooks/start/<journey id>' \--header 'mmApiKey: <MAILMODO_API_KEY>' \--header 'Content-Type: application/json' \--data-raw '{   "email": "email for journey",   "data": {       "personalisation_param1": "value 1",       "personalisation_param2": "value 2"   }}'

 to be passed in the 'data' in the form of a 'key-value' pair. These are meant to assign values to personalization used in the subject line/ body of the mail. For eg. {"firstName" : "John" }

You may need to abort/terminate a running journey on a particular event (eg. customer completes a CTA) or after a fixed time (if set in journey). You can use the Abortapi below to do that-

 https://api.mailmodo.com/hooks/abort/<journeyid>

curl --location --request POST'https://api.mailmodo.com/hooks/abort/<journey id>' \--header 'mmApiKey: <MAILMODO_API_KEY>' \--header 'Content-Type: application/json' \--data-raw '{"email": "email to be aborted","reason":"reason to abort"}'

Trigger journey through API

In this article, we will see how to create journeys in Mailmodo triggered by events recorded in GetResponse via Zapier.

  Open your Zapier account and click on create Zap.

  If this is your first time connecting GetResponse with Zapier it will ask for an API Key which can be found on GetResponse website go to -> tools -> Integrations -> API.

 Now, select the list of contacts in GetResponse that you want to send campaigns to.

 Copy paste the API key we copied and saved before from Mailmodo.com.

Select the Campaign you created previously on Mailmodo. Select the Email id field. ( Make sure that the email field on your website/form/landing page is filled at least once before starting this process )

  Click on Test and Continue and Publish zap.

If you face any problem then reach out to us at 

Trigger Journeys through GetResponse on Mailmodo

In this article, we will see how to create journeys in Mailmodo triggered by events recorded in Webflow via Zapier. 

 Open your Zapier account and click on create Zap.

 Select your trigger event. Make sure the parameters are once submitted before beginning the process.

 Select Authorize Application to grant access to your website.

 Next, select your form, and click continue.

 Click test trigger, this will conduct a test and verify if all details are correct.

 Next, select Mailmodo. You will be asked to sign in. Here, you need to paste the API key that you copied from Mailmodo. 

You can access the API key anytime by going to the 'Integrations' tab in Mailmodo, and clicking on 'See details' under Zapier.

- Paste the API key in the box. Then click on 'Yes, Continue'.

 Select trigger journey and connect your Mailmodo account.

 Next, select the journey you created. Email Id-> Select the Data Email. Make sure that the email field on your website is filled at least once before.

 Test and Continue and Click PUBLISH ZAP.

Trigger Journeys through Webflow on Mailmodo

In this article, we will see how to create journeys in Mailmodo triggered by events recorded in Typeform via Zapier. 

 Click on test trigger to confirm if the right account is connected.

 Next, select Mailmodo. You will be asked to sign-in. Here, you need to paste the API key that you copied from Mailmodo. 

 Journey -> Select the Mailmodo journey you want to trigger.

Email Id-> Select your Email field, and make sure your form is once submitted before the process.

Recipient List -> Select your Mailmodo List you want to add the contact details to.

Trigger Journeys through Typeform on Mailmodo

In this article, we will see how to create journeys in Mailmodo triggered by events recorded in Jotform via Zapier. 

 Select Jotform and select your trigger event.

 Click on test trigger to confirm if the right account is connected.and click continue.

Email Id-> Select your Email field, and make sure your form is once submitted before the process. Recipient List -> Select your Mailmodo List you want to add the contact details to.

 Click continue, then test it and publish your ZAP.

Trigger Journeys through Jotform on Mailmodo

In this article, we will see how to create journeys in Mailmodo triggered by events recorded in GetSiteControl via Zapier. 

 Select Getsitecontrol and select your trigger event.

In this article, we will see how to create journeys in Mailmodo triggered by events recorded in Jotform via Zapier.

 Next, Connect your Getsitecontrol account and click continue.

 Next, select your site and the widget you are connecting to.

 Next, Click on test trigger to confirm if the right account is connected and click continue.

 Next, select  Mailmodo. You will be asked to sign-in. Here, you need to paste the API key that you copied from Mailmodo. 

 Select Trigger Journey and press continue.

 Next, select the Mailmodo account you want to connect to.

Email Id-> Select your Email field, and make sure your form is once submitted before the process. 

Trigger Journeys through GetSiteControl on Mailmodo

2. Selecting the recipient audience. This can be done through-

Below is the request structure for triggering and aborting journeys through API:

 You need to include this before each API endpoint to make API calls.

https://api.mailmodo.com/hooks/start/<journey

https://api.mailmodo.com/hooks/abort/<journey

Mailmodo APIs are completely RESTful. All Mailmodo APIs are authorized via an API key.

 to view the default API key. (You may also create a new API Key by clicking on the 'Add new API Key' button)

curl --location --request POST 'https://api.mailmodo.com/hooks/start/<journey id>' \
--header 'mmApiKey: <MAILMODO_API_KEY>' \
--header 'Content-Type: application/json' \
--data-raw '{ "email": "email for journey", "data": {
"personalisation_param1": "value 1", "personalisation_param2": "value 2" }
}'

curl --location --request POST 
'https://api.mailmodo.com/hooks/abort/<journey id>' \
--header 'mmApiKey: <MAILMODO_API_KEY>' \
--header 'Content-Type: application/json' \
--data-raw '{ "email": "email to be aborted",
"reason":"reason to abort"
}'

Trigger Journeys via API

trigger will allow the contact that has been added or removed from the segment selected, to enter the journey. We will allow you to either create a segment or choose from the existing segment that you have created on Mailmodo. This is best for lead nurturing, onboarding campaigns, promotional marketing, etc. 

You can use this to trigger a loyalty program journey to users who have submitted a form in your feedback emails more than twice in the last 60 days or attended more than 3 events in the past 2 months.

You must have defined segments in your email list, with clear criteria for contacts to enter or leave these segments.

Mailmodo supports creating segments based on ‘User property’, ‘Campaign Activity’, ‘Custom Events’, ‘Shopify Activity’, etc. You can learn more about the segment 

To set up a journey based on segment membership trigger follow these steps:

 Click on ‘Create journey’ on the journey page

 Select ‘Contact enters or leaves a segment ‘ as a trigger.

First select whether you want to trigger the journey for a contact who has entered or left a segment based on your use case. 

Select from the existing lists from the dropdown or create a new one by clicking on the "Create a new list" button

 Design the complete journey and click on the Next button. 

You can review all the important details of the journey at one glance, such as the segment selected, nodes used, testing the journey, and so on to see if they match your requirements perfectly. 



Once the journey is published, new contacts matching the trigger condition will be automatically enrolled. 

Depending upon the no of contacts you have in the system, it might take up to 60 minutes for users to be enrolled in the journey once the contacts meet the segment conditions.
For instance, if a user enters a segment at 5:00 PM, the contact will likely be enrolled in the journey by 6:00 PM at the latest.

 After publishing, the journey will go into the ‘processing’ stage first for checking existing segment membership and a few minutes later the status will be set as ‘running’. Users will start getting enrolled in the journey once the journey moves to a ‘running’ state.

Trigger Journey based on Segment Membership

trigger lets you automate email flows based on the date contact property of your audience like birthday or anniversary. This is best for birthday or anniversary wishes, payment renewal, and so on. 

Once a journey is created using this trigger, it will keep enrolling contacts to the journey every year every month, or just once depending on your use case. 

For e-commerce businesses, you can use this trigger to celebrate the anniversary of a customer's first purchase by sending them anniversary emails with loyalty rewards, thank-you messages, or exclusive offers.

 Go to the Journey section in Mailmodo app and click Create Journey button.

 Choose ‘Occurrence of a date’ as the trigger

 As the next step, set the frequency for this trigger - once, monthly, or yearly.

They can be used in the scenarios as shown below:

 - For one-time events like policy maturity date. Here, the exact date will be matched to trigger the journey

 - For monthly payment reminders, subscription renewal, etc. Journey will be triggered once per month on the day of the month specified

 - For anniversaries, birthdays, or events that occur every year. The journey will be triggered every year on the month and day specified.

 Next, set the number of days you want the journey to be triggered before the contact property date. For instance, you may wish to start sending a series of emails 7 days before the anniversary date of a user. In such a case, the days should be set as 7. 

If you want to trigger the journey on the same date, set it as 0.

Choose the contact property for which you wish to set the trigger e.g. birthday, payment date, anniversary date, etc. Here only those properties will be shown whose data type is date.

After this, set a specific time and time zone. The journey will be triggered at that specific time for the contacts who qualify for that date.

 Lastly, choose the contact list for which you want to check the date property. Please note, that we only support lists and not segments here. Click save and your trigger is configured.

 Now, design your journey with action blocks, delays, and conditions. Once done, before publishing, enable multi-enrolment to trigger this journey at every date occurrence.

Once published, your journey will be in running status. It will start querying for contacts that qualify for that particular date and enroll them in the journey. 

It may take up to 24 hours to enroll a contact in the journey for any change in date property i.e. Let’s assume there is a contact A with a birthday on 30th January. 

Assume today is the 26th of January and you update the birthday to the 26th of January, the contact will not be enrolled in the journey on the 26th. But if you update the birthday date to the 28th ( having more than 24 hours of gap) the contact will be enrolled in the journey on the 28th.

What if the contact property date is on 31st of the month and the frequency is monthly?

If the current month doesn’t include that day (e.g. there is no September 31st ) then we will trigger the journey on the last day of the month. The same applies for a scenario where the date is 29th of February.

What will happen if the date for a contact is not present in the contact property or not in the proper format?

We will ignore such cases. Please check 

 guide for supported date properties in our system

3. What will happen if I set the enrollment as one-time in the Journey settings?

The journey will not be triggered again for any contact which matches the date criteria. Hence, monthly/yearly recurring reminders will not work. For frequency set as ‘Once’ there will be no effect.

4. If I update the date in the contact property after the journey is published how will my journey behave?

Ideally, if the date for the journey trigger is in future, the contact will be enrolled in the journey.

Let’s assume there is a user A with birthday on 30th January. Assume today is 26th of January and you update the birthday to 28th January, the user will be enrolled on the 28th. However, if you update the birthday to 25th January then the user will not be enrolled.

The same logic further applies when you have some offset time set (e.g When to trigger days is set as 3 days) If the (updated date - offset) is in the past then the journey will never be triggered for the contact.

For e.g. let's say offset is set for 10 days and the birthday is updated on 15th Aug 2023 to 23rd August 2023, since the 13th Aug (13 - 10) is in the past, the journey will not be triggered for that year

5. Once the journey is published, If I update the contact property on the same date as the journey trigger date, what will happen?

If the contact property is updated before the specified trigger time for the campaign, it will trigger the journey for the user on the same day. Here the date in the attribute matches the criteria and the trigger time has not passed yet. However, If the property is updated after the specified trigger time for the campaign, it will not trigger the journey

Trigger nodes in the journey