Resources · Make integration

Dynosend Make integrationAutomate Dynosend with Make.

Can Make keep your Dynosend audience up to date on its own? The Dynosend Make integration gives you 8 action modules, all built around contacts and events. This guide shows how to link your account, then walks you through a first scenario that feeds Dynosend from another tool.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Dynosend Make integration let you automate?

The Dynosend Make integration lets a Make scenario (the automation you build, a chain of steps) act on your Dynosend contacts: add them, change them, tag them, subscribe them or remove them. Each step is a module, one brick of the scenario, and Dynosend brings 8 of them, all actions.

Capture leads from your forms. When a signup lands in another app, Create a contact adds the person to Dynosend, then Tag a contact marks where the lead came from, so your campaigns can target that source later.

Keep profiles in sync with your CRM. A deal changes stage elsewhere: Retrieve a contact pulls the matching Dynosend profile and Update a contact writes the new details, so the email tool never lags behind sales.

Feed behavior into your emails. After a purchase or a booking in another tool, Perform an event records it for that contact, and Subscribe a contact can put a new buyer on your list in the same run.

Know the limits first. Dynosend has no trigger in Make, so a scenario starts from another app or from a schedule. Make also publishes only limited documentation for Dynosend, so test every module with real data before you rely on it. If you are new to the editor, the Make training covers the basics, and Make troubleshooting helps when a run fails.

Many apps also have an n8n node. If you are weighing both tools, read n8n vs Make before you build.

Connect

How do you connect your Dynosend account to Make?

  1. 01

    Add a Dynosend module

    In a scenario, click the +, search for Dynosend and pick any module, for example Create a contact. Then click Create a connection. A connection is your Dynosend account linked to Make once, reused by every Dynosend module afterward.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, which helps when you manage several accounts. Then authorize Make on the Dynosend page that opens, or paste the key Dynosend gives you, depending on what the connection window asks for.

  3. 03

    Save the connection

    Click Save. Make now holds the link to your account, and the next Dynosend module you add will offer this connection in its list, so you never repeat the setup inside the same scenario.

First scenario

Your first scenario: turn new leads into tagged Dynosend contacts

GoalWhen a lead arrives in another app, Make creates the contact in Dynosend and tags it with its source.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since Dynosend has no trigger, start with the app where your leads arrive, such as your form tool, and connect it.

  2. 02

    Add Create a contact

    Click the + to the right of the first module, search for Dynosend and choose Create a contact. Pick your connection, then map the lead's details from the previous module into the fields Make shows.

  3. 03

    Tag the new contact

    Add Tag a contact after it. Map the contact returned by Create a contact, then set the tag that names the lead source, so segments in Dynosend stay readable.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received, a bundle being one item passed along, here one lead.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on. Each module run counts as an operation on your Make plan.

Modules

What each Dynosend module does

Dynosend gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Dynosend1

Create a contact

ActionIn the docs only

Adds a new person to your Dynosend audience, using data mapped from an earlier module, so a signup somewhere else becomes a reachable contact.

When to use it
right after a form, a checkout or a CRM step hands you a lead who is not in Dynosend yet.
Watch out
run it on a real test lead first, because Make's documentation for Dynosend is limited and says nothing about duplicates.
Dynosend2

Delete a contact

ActionIn the docs only

Removes a contact from Dynosend, which keeps your audience clean when someone leaves your records elsewhere or asks to be erased.

When to use it
when a customer closes their account in your main tool and should disappear from your mailing base too.
Watch out
treat a deletion as final. Test the scenario on a throwaway contact and check which record you map before switching it on.
Dynosend3

Make an API call

ActionIn the docs only

Reaches any endpoint of the Dynosend API through the connection you already set up, so you can cover what the seven other modules leave out.

When to use it
when you need a Dynosend feature that no listed module offers and you know which API endpoint handles it.
Watch out
you write the request yourself, so keep the Dynosend API reference open while you fill in the module.
Dynosend4

Perform an event

ActionIn the docs only

Going by its name, this module records an event against a contact in Dynosend, which lets your emails react to what that person just did in another tool.

When to use it
after a purchase, a booking or a download captured by a different app in the same scenario.
Watch out
Make gives no official description for it, so check the result in Dynosend after your first Run once.
Dynosend5

Retrieve a contact

ActionIn the docs only

Fetches one contact from Dynosend and hands its details to the next modules, so you can read a profile before deciding what to change.

When to use it
before Update a contact or Tag a contact, when a later step needs values stored in Dynosend.
Watch out
it works on one contact, not a list, so each lookup costs an operation on your plan.
Dynosend6

Subscribe a contact

ActionIn the docs only

Judging by its name, it subscribes a contact in Dynosend, which means a buyer or a lead can start receiving your emails without anyone clicking in the app.

When to use it
once a person has given consent in your form or checkout and you want the scenario to finish the job.
Watch out
the documentation is limited, so confirm in Dynosend after a test run that the contact appears where you expect.
Dynosend7

Tag a contact

ActionIn the docs only

Labels a Dynosend contact with a tag, giving your segments and campaigns a clean way to tell sources, interests or customer stages apart.

When to use it
just after Create a contact, to record which form or channel brought the person in.
Watch out
agree on tag names with your team before building, because a typo in the scenario creates a label nobody filters on.
Dynosend8

Update a contact

ActionIn the docs only

Changes the details of an existing Dynosend contact, so what your team edits in another tool also reaches your email tool.

When to use it
when your CRM or billing tool edits a record and Dynosend should follow without a manual export.
Watch out
map the right contact first, often with Retrieve a contact, or you may overwrite someone else's profile.
Need help

Need help automating Dynosend with Make?

A person reads every message.

FAQ

Questions about the Dynosend Make integration

01Is the Dynosend Make integration free?
Yes, Dynosend is a standard app, so it works from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Make counts usage in operations, one per module run. This page does not cover the price of Dynosend itself.
02What does connecting Dynosend to Make require?
A Dynosend account and a Make account are enough to start. Add any Dynosend module, click Create a connection, optionally name it, then authorize Make on the Dynosend page or paste the key the app gives you, and click Save. Make's documentation for Dynosend is limited and lists no other prerequisite, so if the window asks for something unexpected, check the settings of your Dynosend account. The same connection then serves all 8 modules.
03Does the Dynosend Make integration have a real-time trigger?
No, Dynosend has no trigger in Make at all, neither scheduled nor instant. Your scenario therefore starts elsewhere: on a trigger from another app, such as a form tool or a CRM, or on the schedule of the first module, which is every 15 minutes by default on a new scenario. Dynosend modules then come after that first step and act on the contact data it provides. If another app can call Make through a webhook, its instant trigger lets your Dynosend steps run as soon as it fires.
04What if a Dynosend feature is missing from the Make modules?
Use Make an API call. This module reaches any endpoint of the Dynosend API with the connection you already created, so a feature that the seven other modules skip is still within reach. You will need the Dynosend API reference to write the request. Keep in mind that Make publishes only limited documentation for this app, which is why a test with Run once matters before you switch a scenario on. If the API does not offer the feature either, another app may be a better fit for that step.
05Make or n8n for Dynosend: which one fits better?
It depends on where the rest of your automations live. On Make, Dynosend comes with 8 action modules, including Make an API call, and no trigger, so every scenario starts from another app or a schedule. Many apps also have an n8n node, so check whether Dynosend has one before you choose. If your other scenarios already run in Make, keeping Dynosend there means one editor and one set of connections. The team's comparison page sets out the criteria between the two tools without ranking them.