Resources · Make integration

SuiteDash Make integrationAutomate SuiteDash with Make.

Tired of copying new clients into SuiteDash by hand? The SuiteDash Make integration gives you 10 modules: 7 actions and 3 searches on contacts and companies. This guide shows you how to link your account, build a first flow and pick the right module.

Try the SuiteDash integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SuiteDash Make integration do for you?

The SuiteDash Make integration lets Make write to and read from your SuiteDash portal: it creates, updates and looks up contacts and companies, and adds people to your marketing audiences. You build it as a scenario, which is the automation you assemble in Make from modules, the small bricks that each do one job.

Client intake with no retyping. When a new customer appears in another tool, a scenario runs Create a Company for the business and Create a Contact for the person, so your team finds a complete record in SuiteDash instead of a sticky note.

Records that stay current. A phone number changes in your billing app? Get a Contact reads the SuiteDash record by its ID, then Update a Contact writes the new value. Update a Company does the same on the business side.

Audiences filled as you go. Subscribe Contacts to Marketing Audiences puts a fresh client straight into the right list, and List Contacts pulls your contacts out when a report or another tool needs them.

One thing Make cannot do here: SuiteDash has no trigger module, so a SuiteDash event will not start a scenario by itself. The flow starts from another app or from Make's schedule. If you are weighing both tools, n8n vs Make lays out the criteria. To learn the editor properly, see our Make training, and check Make pricing before you scale up.

Connect

How do you connect SuiteDash to Make?

  1. 01

    Copy your two API keys

    In SuiteDash, open the Flyout Menu, click Integrations, then choose Secure API at the top of the page. Copy the key labeled Public ID and the one labeled Secret Key. You need an active SuiteDash account to see them.

  2. 02

    Add a SuiteDash module

    In your Make scenario, add any SuiteDash module and click Create a connection. A connection is your SuiteDash account linked to Make once; every SuiteDash module in your scenarios reuses it afterward.

  3. 03

    Paste the keys and save

    Give the connection a name in Connection name if you like (it is optional, but handy with several portals), paste the Public ID and the Secret Key, and follow the on-screen instructions to finish.

First scenario

Your first scenario: turn a new lead into a SuiteDash contact

GoalWhen a new lead arrives in another app, Make creates the contact in SuiteDash and subscribes them to a marketing audience.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since SuiteDash has no trigger, pick the trigger of the app where your leads land, such as your form tool.

  2. 02

    Add Create a Contact

    Click the + to the right of that first module, search for SuiteDash and choose Create a Contact. Select your connection, or create it with the steps above.

  3. 03

    Map the lead's details

    Fill the module fields by mapping data from the first module: you click a field and pick the value the lead left. Each lead travels as one bundle, meaning one item passed from module to module.

  4. 04

    Subscribe the new contact

    Add Subscribe Contacts to Marketing Audiences after it, and map the contact that Create a Contact just returned, so the person joins the audience you choose.

  5. 05

    Test with Run once

    Click Run once and send one test lead. Read the bundles each module received, then check that the contact shows up in SuiteDash.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan.

Modules

What each SuiteDash module does

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

SuiteDash1

Create a Company

Action

In Make“Creates a new company.”

Opens a new company record in SuiteDash, so the business behind a deal has its own place next to the people who work there.

When to use it
when a new B2B client signs and you want the organization set up before you attach contacts to it.
Watch out
if the same company can reach the scenario twice, run List Companies first to see whether it already exists.
SuiteDash2

Create a Contact

Action

In Make“Creates a new contact.”

Adds a new person to your SuiteDash portal, so a lead or client captured in another tool is ready for your team without anyone retyping their details.

When to use it
right after a form reply, a booked call or a signed quote in the app that starts your scenario.
Watch out
when duplicates are a risk, place List Contacts before it and only create the person if the search comes back empty.
SuiteDash3

Get a Company

Action

In Make“Retrieves an existing company by its ID.”

Fetches one company from SuiteDash using its ID and hands its data to the next module, which saves you from searching through the whole list.

When to use it
when another step already stored the company ID and you need its current details, for instance to fill a document or a message.
Watch out
it needs the exact ID; if all you have is a name, start with List Companies.
SuiteDash4

Get a Contact

Action

In Make“Retrieves an existing contact by its ID.”

Reads a single contact by its ID and gives you everything SuiteDash holds on that person for the rest of the scenario.

When to use it
before an update, to compare what SuiteDash has with the new value coming from your other app, or to pull a contact's details into an email.
Watch out
the ID is the key here, so keep it somewhere your other tools can pass back to Make.
SuiteDash5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the SuiteDash API from your scenario, with the same connection as the other modules, so you are not stuck when a listed module falls short.

When to use it
when the task you need goes beyond contacts, companies and audiences, the areas the nine other modules cover.
Watch out
you write the request yourself, so keep the SuiteDash API documentation open while you set it up.
SuiteDash6

Update a Company

Action

In Make“Updates an existing company by its ID.”

Changes an existing company in SuiteDash, found by its ID, so its record keeps up with what happens in your other systems.

When to use it
when a client moves offices or changes its legal details in your invoicing tool and SuiteDash should follow.
Watch out
it edits the company whose ID you map, so a wrong ID overwrites another client; test with Run once on a dummy record first.
SuiteDash7

Update a Contact

Action

In Make“Updates an existing contact by its ID.”

Writes new values onto a contact that already exists, located by its ID, which keeps one clean record per person instead of a pile of duplicates.

When to use it
when someone updates their email or job title in a form or in your CRM and your portal should show the same thing.
Watch out
pair it with List Contacts or Get a Contact when your source app does not know the SuiteDash ID.
SuiteDash8

List Companies

Search

In Make“Retrieves a list of companies.”

Returns the companies in your SuiteDash account as a set of bundles, one per company, ready to be filtered, counted or copied elsewhere.

When to use it
to find a company's ID before a Get or an Update, or to send your client list to a spreadsheet for a review.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per company it finds.
SuiteDash9

List Contacts

Search

In Make“Retrieves a list of contacts.”

Pulls the contacts stored in SuiteDash out as separate bundles, which is how you check who already exists or feed people into another tool.

When to use it
as a guard before Create a Contact, or when a mailing app or a report needs your SuiteDash contacts.
Watch out
when nothing matches, the modules after it simply do not run, so plan what the scenario should do in that case.
SuiteDash10

Subscribe Contacts to Marketing Audiences

Search

In Make“Subscribes contacts to marketing audiences.”

Places contacts into the marketing audiences you set up in SuiteDash, so your campaigns reach new clients without a manual import.

When to use it
just after Create a Contact, when a lead from a webinar sign-up or a purchase should start getting the matching emails.
Watch out
Make lists this module among the searches, so read what it returns during Run once before you map its output further.
Need help

Need help automating SuiteDash with Make?

A person reads every message.

FAQ

SuiteDash and Make: common questions

01Is the SuiteDash Make integration free?
Yes, on the Make side. SuiteDash is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, cannot run a schedule more often than every 15 minutes, stops a run after 5 minutes and caps data transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and allow unlimited active scenarios. You still need your own active SuiteDash account, which SuiteDash bills separately.
02What do you need to connect SuiteDash to Make?
An active SuiteDash account and its API keys. In SuiteDash, open the Flyout Menu, go to Integrations, then Secure API, and copy both the Public ID and the Secret Key. In Make, add any SuiteDash module, click Create a connection, optionally name it, and paste the two keys, each in its own field. The connection is then reused by every SuiteDash module you add later, in this scenario and in the next ones.
03Can the SuiteDash Make integration react in real time?
No, not from SuiteDash itself. The app has no trigger module, scheduled or instant, so nothing that happens inside SuiteDash can start a scenario. You start the flow another way: with a trigger from the app where the data originates, such as your form or payment tool, or by letting Make run the scenario on its schedule, every 15 minutes by default. In both cases the SuiteDash modules act as the next steps.
04What if a SuiteDash module is missing in Make?
Use Make an API Call. It reaches any endpoint of the SuiteDash API with the connection you already set up, so you can cover what the 10 listed modules leave out, for example data outside contacts, companies and audiences. You will need to write and test the request yourself from the SuiteDash API documentation. Test your request with Run once. Also note that Make flags its SuiteDash documentation as AI-generated, so confirm important details with SuiteDash.
05Should you use Make or n8n for SuiteDash?
It depends on the tool your team already knows. On Make, SuiteDash comes with 10 modules for contacts, companies and marketing audiences, plus Make an API Call for the rest, and it runs from the Free plan. Many apps also have an n8n node, so check whether one exists for SuiteDash and what it covers before you decide. Compare the modules you actually need on each side rather than the brand.
Same platform

Other docs you might need on this stack.

Browse all integrations