In magnews, automated flows take shape thanks to nodes. You can think of them as the building blocks of the flow: each node represents a single step and tells the platform what should happen at that specific point in the journey.
A node can intercept an event, perform an action, or manage a decision. By connecting multiple nodes one after another, you can build simple automated flows or more advanced multichannel automations that adapt to your contacts’ behavior, data, and timing.
To keep everything clear and easy to read, magnews groups nodes into three main types:
Event nodes
Action nodes
Decision nodes
Event nodes
Event nodes are used to intercept something that happens. They can be related to a contact, a data record, an interaction, or an external trigger such as an API call or a web tracking event.
The automated flow starts when the event occurs. Event nodes represent the trigger of the flow and are ideal when you want to react automatically to a behavior or a change, without manual intervention.
New contact
This node starts the automated flow when a contact is added to the database with status Subscribed, or when the contact changes to Subscribed from Unconfirmed, Suspended, or Unsubscribed.
It’s typically used to intercept new subscriptions or reactivations, for example when a contact signs up online and automatically enters the welcome flow.
To learn more, go to the dedicated page.
Contact update
The automated flow starts when one or more contact fields are updated. This is useful to react to data changes and trigger automations based on specific updates.
For example, if a contact exceeds a purchase threshold, the free shipping field can be updated to let the contact enter the flow.
To learn more, go to the dedicated page.
Contact date event
This node starts the automated flow on the date stored in a contact field. It’s ideal for managing deadlines, reminders, or date-based communications.
For example, an insurance company can send a reminder 10 days before a policy expires.
To learn more, go to the dedicated page.
Contact anniversary
The automated flow starts on each anniversary of the date stored in a contact field. You can use it for recurring, time-based communications.
For example, three days before a birthday you can send an email with a dedicated promo code.
To learn more, go to the dedicated page.
Periodic filter
This node starts the automated flow for all contacts that match a filter at a specific time or on a recurring schedule. It’s useful for periodic checks on groups of contacts.
For example, you can intercept subscriptions that are about to expire by setting a monthly frequency with recurrence on the 20th day.
If you change the recurrence settings, the recalculation takes place on the next date that matches the configured frequency.
To learn more, go to the dedicated page.
New data event
The automated flow starts when a new item is added to a data table.
This node is designed to work with structured data rather than directly with contacts. For example, it’s useful when adding a new record needs to trigger an automation linked to associated contacts.
Data periodic filter
This node periodically starts the automated flow for each data table item, linked to contacts, that matches the defined criteria.
It’s ideal when you want to regularly check data status and trigger automations only for relevant items.
To learn more, go to the dedicated page.
Button action
The automated flow starts when a contact submits a form by clicking the submit button associated with an action.
For example, after completing a satisfaction survey, you can automatically send a follow-up email to the contact.
Post-click action
This node starts the automated flow when a contact clicks on a link associated with an action.
For example, clicking a link can update a database field or start a dedicated path based on the interest shown.
Web tracking event
The automated flow starts when a contact visits a specific web page.
For example, if a contact visits the courses page of your e-learning site, you can send a follow-up email a few days later to encourage a purchase.
To learn more, go to the dedicated page.
User request
This node starts the automated flow when a platform user manually triggers it from the contact profile.
For example, after a phone interview, an operator can start the flow to send a follow-up questionnaire by email.
Automated flow event
The automated flow starts when it is triggered by another automated flow. This is useful to connect multiple automations and build modular journeys.
For example, when the welcome flow ends, you can automatically start the loyalty program flow, opening a new session for the contact.
API event
This node starts the automated flow following a call from a web service or an external app, using the event ID.
For example, after completing a survey in an external app, you can start a flow that sends an email to the contact.
Action nodes
Action nodes define what magnews should do automatically within the automated flow. This is where something concrete happens: sending a communication, updating a contact, changing an audience, or starting another automated flow.
Each action node performs a specific, controllable operation. By placing them at the right point in the flow, you can orchestrate communications and updates in a way that stays consistent with the contact’s journey, while keeping the automated flow clear and easy to follow even as it grows more complex.
Send message
This node sends an email or an SMS to the contact at the point in the automated flow where it is placed.
It’s the main node for direct communication and can be used in simple flows as well as in more advanced automations.
For example, when a contact signs up online, they can automatically receive a subscription confirmation email.
To learn more, go to the dedicated page for email sending and the dedicated page for SMS sending.
Send private message
This node sends a notification email to a specific email address, different from the contact’s address. It’s designed for internal or service notifications.
For example, if a contact doesn’t open an email after three days, you can send a notification to their account manager suggesting they reach out.
Q Message 
With this node, the contact receives the message that has the highest probability of maximizing the automated flow’s success. Magnews automatically selects the most effective variant based on the available data.
It’s useful when you want to optimize message performance without manually choosing the content.
To learn more, go to the dedicated page.
Update contact
This node updates one or more contact fields while the automated flow is running. It’s useful to keep data aligned with the actions or events happening in the flow.
For example, after each purchase you can increase the value of the fidelity card field.
To learn more, go to the dedicated page.
Update contact status
This node updates the contact’s status when specific conditions are met within the automated flow.
For example, you can change a contact from Unconfirmed to Subscribed when they click the registration link for a communications service.
Add/remove from audience
This node adds or removes the contact from a static audience. It’s useful for segmenting contacts based on their behavior or on where they are in the journey.
For example, if a contact doesn’t interact with a communication, you can add them to an audience dedicated to specific retargeting activities.
To learn more, go to the dedicated page.
Update variable
This node assigns a value to an automated flow variable. Variables let you store temporary information that’s useful for logic and calculations within the flow.
For example, each time a contact moves from Basic to VIP status, you can update the variable that tracks the total number of VIP contacts.
To learn more, go to the dedicated page.
Start another flow
This node starts a new session of another automated flow for the contact and must be used together with the Automated flow event node, which receives the start request.
For example, at the end of the welcome flow you can start the loyalty program flow, creating a new session for the contact. The contact can enter the new flow only if the previous session exited with status Success.
Stop another flow
This node stops active sessions of another automated flow for the contact. It’s useful when a new condition makes it unnecessary to continue an automation that is already running.
For example, if a contact moves to VIP status, you can stop the loyalty program flow.
Run API request
This node lets the automated flow communicate with external systems through a REST API call. You can use it to send data, sync platforms, or trigger custom processes at the exact moment a contact reaches a specific point in the flow.
For example, you can use it to send a contact’s data in real time to an external CRM, update a ticketing system, or notify an e-commerce app, while keeping full control over the exchanged data and how responses are handled directly within the flow.
Learn more on the dedicated page.
Decision nodes
Decision nodes manage timing, conditions, and branching within the automated flow. This is where the flow can pause, wait, check a condition, or choose which path to follow based on data or behavior.
These nodes allow the automated flow to adapt: not all contacts have to follow the same path at the same time. With decision nodes, you can create time-based waits, check interactions, split the flow into multiple branches, or repeat part of the journey. They’re what makes automation truly flexible and able to react to what happens along the journey.
Wait
This node pauses the contact’s session for a defined period of time. When the wait ends, the automated flow resumes following the configured path. It’s the basic node for managing timing.
For example, after a purchase you can wait a few days before sending a satisfaction questionnaire, giving the contact time to use the product.
To learn more, go to the dedicated page.
Q Wait
This node makes the contact wait for the amount of time that has the highest probability of maximizing the automated flow’s success. Session distribution changes automatically, assigning more contacts to the timing options that have produced better outcomes in the past.
It’s useful when you want to optimize timing without defining it manually.
To learn more, go to the dedicated page.
Wait for message activity
This node checks whether the contact performs a specific interaction with a message within a defined time window, such as opening an email, clicking a link, message delivery, or a recorded bounce.
The contact exits through Yes as soon as the action occurs, or through No if the time window ends without the interaction.
For example, you can check whether the contact clicked an email requesting information within a certain period.
To learn more, go to the dedicated page.
Wait for response
This node checks whether the contact completes a specific landing page within the configured time frame. The contact exits through Yes as soon as they submit the landing page, or through No if they don’t respond within the set limit.
It’s useful for managing follow-ups related to surveys, information requests, or sign-ups.
To learn more, go to the dedicated page.
Message activity
This node routes the contact based on the interaction recorded for a specific message, allowing the flow to proceed differently depending on what the contact did.
It’s recommended to use it together with the Wait node, so the contact has enough time to read, click, or otherwise interact with the communication. For example, if the contact opens an email you can send a read-notification message.
To learn more, go to the dedicated page.
Check condition
This node checks whether a specific expression or filter evaluates to true. The contact exits through Yes when the condition is met; otherwise, they follow the alternative path.
For example, you can check whether the contact meets specific criteria or requirements.
To learn more, go to the dedicated page.
Check multiple conditions
This node evaluates multiple conditions and routes the contact to one of the configured exits, based on the rules you set.
For example, you can branch the automated flow based on the contact’s points balance:
- if it’s above a certain threshold, you can mark them as VIP
- if it falls within a mid-range, you can send a promotional email
- if it’s below a minimum threshold, you can start a loyalty program automated flow
To learn more, go to the dedicated page.
Check response
This node routes the contact based on the answer given to a specific question. It’s useful for creating different paths based on the choices or preferences expressed by the contact.
To learn more, go to the dedicated page.
Q Catch
This node automatically classifies the contact’s response to a landing page and routes them based on the assigned category. It’s designed to interpret responses and send the contact down the most appropriate path.
To learn more, go to the dedicated page.
Random decision
This node randomly routes the contact through one of the configured exits, based on a defined probability.
By default, there are two possible exits, each with a 50% probability, but you can add more exits and adjust the percentages as you like.
For example, you can diversify the contact journey by creating three branches and distributing contacts randomly: 15% into the first branch, 50% into the second and the remaining contacts into the third one.
Q Split
This node routes the contact through the exit that has the highest probability of maximizing the automated flow’s success. Session distribution is updated automatically, favoring the paths that have produced better outcomes.
It’s ideal for optimizing flows over time without manual intervention.
To learn more, go to the dedicated page.
Contest
This node routes contacts through the configured exits based on their order of arrival.
For example, you can assign:
- a 30% discount to the first 100 contacts who complete a questionnaire
- a 15% discount to the next 100
- a 10% discount to everyone else
Loop
This node lets the contact repeat part of the automated flow a fixed number of times. The contact exits through No until the maximum number of iterations is reached.
For example, you can resend a communication multiple times to a contact who hasn’t opened it, up to a set limit.
Exit
This node determines when the contact exits the automated flow and sets the outcome, which is used for reporting. The contact can exit:
- with a positive outcome
- with a negative outcome
- with a neutral outcome
The selected outcome is used to generate automated flow statistics.