Mailmodo 0ff833fb

Mailmodo Support

Raise a Ticket here

Update subscription status action block allows you to update the subscription status of your contacts as they move through the email marketing journey in Mailmodo. It can be useful in scenarios where -

A contact unsubscribed from your emails earlier but recently has shown intent at your website to resubscribe to your newsletter emails


A contact signed up for your webinar events and wishes to receive related emails but wants to be unsubscribed post event completion.

Here is how you can add the block in your journey →

 Go to journey section and create a new journey

 Choose a trigger method of your choice e.g. Contacts added to a list

 Now add Update subscription Status block as shown

 Choose the Unsubscribe Contact /Resubscribe contact option. Select email types for which you want to unsubscribe or resubscribe a contact enrolled in the flow.

 Add your desired action blocks after this depending on your use case. For example, you may add a campaign action block to send a newsletter campaign after resubscribing your contacts to newsletter type of email. Learn more about email types 

 If you wish to unsubscribe the contacts after the journey is completed you may further add another update subscription status block with configuration set to Unsubscribe (with email types of your choice )

 That’s it! Now, you can publish the journey and enroll contacts. 

It may take some time to update the subscription status of contacts. If you intend to add a campaign block immediately after this block, it is recommended to insert a 10-minutes delay block in between. This will provide a safety net for any unexpected delay that may occur.

1. How does subscription status impact enrollment in journey ?

Contacts that are unsubscribed at account level or one or more email types can be enrolled into the journey but they will fail at the send campaign block. Hence, it becomes necessary to resubscribe them using the Update subscription status block if you want to send campaigns to them.

2. What will happen if I choose Unsubscribe to all email types and save?

Once contacts pass through the update subscription block they will be unsubscribed at account level irrespective of their previous subscription status. This means no campaign can be sent to them from Mailmodo until unless they are resubscribed again.

3. What will happen if I choose Unsubscribe to one or more email types and save?

Here is what will happen for different scenarios →

Subscribed users will be unsubscribed to selected email type(s). Hence, any new emails of the selected type will not be sent to those users.


Contacts previously unsubscribed to a particular email type say ‘Product update’ will also be unsubscribed to the new email type (say ‘Newsletter’) configured in the journey. Hence, users will not receive emails of type ‘Newsletter’ and ‘Product update’ going forward.


Contacts unsubscribed at account level will continue to be unsubscribed at account level and hence, will not receive any email.

4. What will happen if I choose Resubscribe to all email types and save?

Once contacts pass through the update subscription block they will be resubscribed to the account level along with all the Email types existing in your account. Hence, the contacts will receive all kinds of emails going forward

5. What will happen if I choose  Resubscribe to one or more email types and save?

Once contacts pass through the update subscription block they will be resubscribed to the account level along with the selected Email types configured in the block. Hence, the contacts will only receive emails of that kind going forward

6. Is there a way I can check the subscription status of my contacts ?

 and check the APIs for that in the contact management section. Also, check 

Update Subscription Status Action block

This guide will walk you through the steps of setting up and using Send SMS action in the Mailmodo platform. 

Before you get started, you need to have a Twilio account to send SMS using Mailmodo. 

Mailmodo doesn’t set up or manage your Twilio account 


While we partner with Twilio to send SMS messages, you’ll have to set up and manage your own Twilio account—including things like adding senders and doing other Twilio specific tasks in your Twilio account. 

Now, that you understand that, let’s get you started using Twilio to send SMS to your customers as part of your Mailmodo journeys.

To get started, you have to do a few things before you start sending SMS: 

If you don't already have one, you'll need to create a Twilio account. We recommend starting with a trial account.

You'll need to obtain a Sender phone number from Twilio. This could be a regular phone number, a short code, or an alphanumeric ID. For a trial account, you get a trial number as well.

Navigate to your Mailmodo integration section. 

You will find Twilio SMS listed as an integration option.  

Add your Twilio Account SID and Auth Token. These credentials can be found in your Twilio dashboard.

Ensure that your contacts' phone numbers are stored as attributes within Mailmodo. You may label them according to their purpose (e.g., primary_phone, cell_phone).

Phone numbers should be stored in E.164 format to ensure compatibility with Twilio. This format includes the country code, area code, and subscriber number.

Once, all that is done, you can start sending SMS. 

Choose the sender ID number or alphanumeric ID from which you want to send the message. This is the same sender ID that you added in Twilio. 

Select the recipient's phone number attribute using the dropdown. 

You can always use personalisation using the $ syntax i.e. ${var} for sending personalised values in the SMS. 

Once you are done, save the block and continue with your journey. You can 

You have the option to use manual sender IDs, including alphanumeric IDs. Be aware of the limitations and requirements associated with these IDs.

Send SMS as an action in a journey

 as an action allows you to update the value of a contact property for the contact of a running journey. 

For example - Use this as an action to update the value of the ‘Conference location’ as per the customer's response in the conference registration form used in the journey. 

 Drag and drop ‘Update contact property’ card from the left panel. 

 Connect it to the relevant card in the journey. 

 Click on the ‘Update contact property’ card to open the right panel.

 Select the relevant contact property from the dropdown and add the new value in the input field. 

 You can also dynamically update the selected contact property when the triggers for your journey are →

For instance, when you use Form Submission as a trigger, you will get the option to add a dynamic value in the Update contact property block. Click on ‘Use dynamic value instead’. You will be prompted to fetch data from a form field used in the journey trigger. Map the contact property with one of the form fields. 

Similarly, when the trigger is ‘Occurrence of an event’ you will be able to map the contact property with event properties.

This feature will be helpful for scenarios where you want to update contact property from a form submission or event update. E.g. You send an AMP form email to your users to update their contact details. Any submission in the email will lead to an update in the contact property of that recipient in the Mailmodo database. The new value will be same as the submission made in the form. Likewise, any events coming for any contact will update the contact property mapped with any event property.

 Click on the ‘Save’ button to complete the configuration. 

This would mean, whenever the contact reaches the ‘Update contact property’ step in the journey, the new value will get updated in the selected contact property for that contact in the journey. 

Update contact property as an action in the journey

Use the send campaign as an action to send emails to contacts in the journey. 

For example - Use this as an action in the signup event journey to send welcome kits to new customers on your platform. 

 Drag and drop the ‘Send campaign’ card from the left panel. 

 Click on the ‘Send campaign’ card to open the right panel. 

 Add the campaign name, subject line, and pre-header text, from the name, reply to email, and select template and sender email to set up the campaign. 

In cases when the template or subject has personalisation parameters, you need to map it in the personalisation popup.

If the trigger is an occurrence of an event and the personalizations are for event properties, use the same personalisation pop-up to select the exact event and map the parameters with the event properties. 

 Click ‘Next’ to map the personalisation in the pop-up and review the added campaign details. 

 Once satisfied with the review page, click the ‘Save’ button in the campaign flow to complete the configuration. 

This would mean, that whenever a contact reaches the ‘send campaign’ step in the journey, an email with the selected template and added details will get triggered. 

Send campaign as an action in the journey

A webhook allows one application (like Mailmodo) to send real-time data to another application or system whenever a specific event or trigger occurs.

Let’s assume you have created a journey with a trigger like a new user signing up, a payment being made, or a form being filled in your campaign. By adding the webhook block in the journey, as soon as a user signs up or matches the trigger, the webhook is triggered. 

This initiates the process of sending a welcome email as soon as a user registers. It ensures that the welcome email is sent in real-time, creating a positive and seamless user experience. Additionally, the webhook can be customized to include specific data or instructions for the welcome email, making it highly personalized for each user.

Some specific examples when webhook can be used are:

When a user subscribes to a newsletter, a webhook can trigger a welcome email sequence.

A webhook can be used to notify a sales team when a lead reaches a certain engagement score, triggering follow-up actions.

When a contact updates their email address on a subscription form, a webhook updates the email address in the company's CRM system. This ensures all systems have the latest contact information.

You want your sales team to reach out to new customers who have signed up for a free trial. You have also noticed that success rates of converting these customers to paid plan increases if the team reaches out within the first 5 hours. 

You decide to connect your welcome flow on Mailmodo to Slack so that your team receives real-time notifications of new signups. To do so, you add a Webhook which connects to a zap (Zapier).

The zap has Send Channel Message(on Slack) as an action.

Your team gets the message and starts preparing to connect with the customer.

By the time the team reaches out, the customer will have already gotten a campaign guiding them about the product and informing them that your team will be connecting. All this is achieved within minutes by using webhooks in journeys.

When creating a webhook, the receiving application must accept POST requests and have an API. In addition, we only support sending HTTPS requests to the default HTTPS port.

 Connect it to the relevant card in the journey as per your requirement.

card which will open a right panel for setting up the Webhook

For setting up the Webhook, you will need to enter the following information:

 Mailmodo needs a URL to deliver requests to. This means you need to set up a URL accessible from the public web. This is usually done through a backend panel or an API.

 You can customize the headers that are sent along with the HTTP request when the webhook is triggered. The following are some of the examples of customer headers:
a. Authentication tokensFor example -
Authorization: Bearer your_api_token_here
b. Specify the format of the data being sent
For example -
Content-Type: application/json

 a. You can also customize and configure the payload which ensures that the information is relevant, well-structured, and protected, promoting efficient data exchange and integration while accommodating various use cases and versions of the recipient application.{  "user": "John Doe",  "email": "johndoe@example.com",  "age": 30}
b. You can add personalization parameters to the payload by adding the '$' symbol. You can also enter the fallback value for the parameter selected.

: Go to the Webhook.site website. The URL is usually something like 

https://webhook.site/your-unique-identifier

. You'll see a screen with a unique URL generated for your testing session.

: Copy the unique URL provided on the Webhook.site page. This URL is where you'll send your webhook data for testing.

Go back to your journey builder and add the Webhook block in the journey. Paste the webhook URL in this webhook block and JSON payload if any. 

: Click on the “Test journey” button on the top right corner in the journey builder enter the email ID (preferably yours) and start the journey.

: Go back to the Webhook.site page in your browser. You should see the details of the webhook request that was sent, including the headers, payload, and any other relevant information.

    If your webhook testing fails, below might be some reasons

Your server is not reachable or the server is currently down. 

Your webhook payload/header validation fails due to some reason. 

Mailmodo domain is not whitelisted in your server so we won't be able to read the webhook response 

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

Send Webhook as an action in a journey

" block as an action adds contacts of a running journey into a particular list. 

Use this as an action in the webinar registration journey and add customers who have registered for the webinar to a list called "Webinar registrations".

 Drag and drop the ‘Add contact to a list’ card from the left panel. 

 Click on the ‘Add contact to a list’ card to open the right panel. 

This would mean, that whenever the contact reaches the ‘Add contact to a list’ step in the journey, the particular will get added to the selected list. 

Add contact to a list as an action in the journey

" block as an action removes contacts in a running journey from any particular list(s). 

Use this action to update your pending payment list via events sent to the platform for the contacts whose payment has been done

 Drag and drop the ‘Remove contact from a list’ card from the left panel. 

 Click on the ‘Remove contact from a list’ card to open the right panel. 

 Select the list in the dropdown from where you wish to remove the contact. 

The contact will now be removed from the chosen list once it reaches the "Remove contact from a list" level in the journey flow. 

Action nodes in the journey