Resources · Make integration

SUMIT Make integrationAutomate SUMIT with Make.

Can Make push work into SUMIT for you? The SUMIT Make integration gives you 8 action modules, from adding a customer to sending an SMS. This guide shows how to link your account, build a first scenario and pick the right module.

Try the SUMIT integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SUMIT Make integration do?

The SUMIT Make integration lets a scenario, meaning the automation you build in Make as a chain of modules, write into your SUMIT account. Each module is one brick of that chain. SUMIT brings 8 of them, all actions: they act when something earlier in the scenario hands them data, and none of them starts a scenario by itself.

New contacts land in SUMIT without retyping. A form tool or a store app starts the scenario, then Create a customer records the person, and Add Recipient to Email Mailing List or Add Recipient to SMS Mailing List puts them on the right list.

Paperwork follows the event that caused it. Create Document produces the document in SUMIT, and Get Document PDF fetches the file so the next module can store it or attach it to an email.

A short text goes out at the right step. Send an SMS can close a flow with a confirmation to the customer.

Know the limits before you start. Make's documentation for SUMIT is marked as limited: it gives no description of the modules, no field list and no connection steps specific to the app. The module names are your main guide, and Make an API Call covers anything the 8 modules leave out. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make review covers the editor itself, and the Make training helps if this is your first scenario.

Connect

How do you connect SUMIT to Make?

  1. 01

    Add a SUMIT module

    In your scenario, click the + and search for SUMIT. Pick any of its modules, then click Create a connection. A connection is your SUMIT account linked to Make once and reused by every SUMIT module afterwards.

  2. 02

    Name the connection

    Make offers a field to name the connection. It is optional, but a clear name such as the company or the account owner helps the day you run several SUMIT accounts side by side in the same Make organization.

  3. 03

    Authorize and save

    Depending on what SUMIT asks for, either approve Make on the SUMIT page that opens or paste the key SUMIT gives you. Then click Save. The module can now read the lists Make is able to load from your account.

First scenario

Build your first scenario with SUMIT

GoalWhen a new client signs up in another app, Make creates the customer in SUMIT and then a document for that customer.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since SUMIT has no trigger, this first module comes from the app where new clients appear, such as your form tool.

  2. 02

    Add Create a customer

    Click the + on the right of that first module, search for SUMIT and choose Create a customer. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the client data

    Fill the module fields by picking values from the first module: the name, the email, whatever the form collected. Each bundle, meaning one item passed from module to module, becomes one customer.

  4. 04

    Chain Create Document

    Add Create Document after the customer module and map what the customer module returned. If the module asks which customer the document belongs to, that output is your answer.

  5. 05

    Test with Run once

    Click Run once, trigger a test signup, then open each module to read the bundles it received. Check in SUMIT that the test customer and document look right before going further.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, or the instant option if that app offers one. Then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What can the SUMIT modules do?

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

SUMIT1

Add Recipient to Email Mailing List

ActionIn the docs only

You get a contact placed on one of your SUMIT email lists without opening SUMIT, as the module name says. It is the natural follow up to a signup or a purchase recorded elsewhere.

When to use it
a visitor ticks a newsletter box on your site and should join the matching email list.
Watch out
the documentation gives no field list, so open the module after connecting to see what it expects.
SUMIT2

Add Recipient to SMS Mailing List

ActionIn the docs only

This one feeds your SUMIT text message lists instead of the email ones, so a phone number collected in another app ends up where your SMS campaigns start.

When to use it
a customer agrees to receive text updates at checkout, and you keep that consent in SUMIT.
Watch out
pick it over the email variant only when the bundle actually carries a phone number.
SUMIT3

Card updated

ActionIn the docs only

The name sounds like an event, yet Make lists no trigger for SUMIT, so this module sits with the actions: it runs when the scenario reaches it and never starts anything on its own.

When to use it
test it first with Run once on a sample record to see which card it updates in your account.
Watch out
the documentation says nothing about what a card is here, so confirm the result in SUMIT before relying on it.
SUMIT4

Create Document

ActionIn the docs only

Here the scenario produces a new document in SUMIT from data mapped out of earlier modules, which saves you from filling the same details by hand each time.

When to use it
right after Create a customer, when the fields let you point the document at the person just added.
Watch out
run it on test data first, since every document it creates is a real one in your account.
SUMIT5

Create a customer

ActionIn the docs only

With this module, a person who shows up in another app becomes a customer record in SUMIT, ready for the documents and messages that follow.

When to use it
a new signup, order or signed quote in another tool should exist in SUMIT too.
Watch out
nothing in the documentation says it checks for duplicates, so avoid sending the same person twice.
SUMIT6

Get Document PDF

ActionIn the docs only

You end up with the PDF of a SUMIT document inside your scenario, as a file the next module can save to cloud storage or attach to an email.

When to use it
after Create Document, when the client should receive the file or your team wants a copy filed away.
Watch out
on the Free plan Make handles files up to 5 MB, which matters for heavy PDFs.
SUMIT7

Make an API Call

ActionIn the docs only

This module reaches any endpoint of the SUMIT API with the connection you already set up, so a need the other seven modules do not cover is still within reach.

When to use it
you need a SUMIT operation that has no dedicated module in the list.
Watch out
you write the request yourself, so keep SUMIT's API documentation open next to the editor.
SUMIT8

Send an SMS

ActionIn the docs only

A text message leaves SUMIT at the exact point of the flow where you place this module, carrying data mapped from the steps before it.

When to use it
confirming to a customer that their document is ready or their record was created.
Watch out
every bundle that reaches it sends one message, so test with Run once on a single item before switching the scenario on.
Need help

Need help automating SUMIT with Make?

A person reads every message.

FAQ

SUMIT and Make: common questions

01Is the SUMIT Make integration free?
Yes, SUMIT is a standard app in Make, so its modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and allow unlimited active scenarios. Your SUMIT subscription is a separate matter that this page does not cover.
02What does the SUMIT Make integration need to connect?
A SUMIT account and a Make account. Make's documentation lists no prerequisite for SUMIT and no app specific steps, so the generic flow applies: add a SUMIT module, click Create a connection, optionally name it, approve Make on the SUMIT page or paste the key SUMIT provides, then click Save. That connection is reused by all 8 modules. If the window asks for a key you do not have yet, fetch it in SUMIT first: Make documents no SUMIT specific setup, so that is the one step you handle on your own.
03Does the SUMIT Make integration react in real time?
No, SUMIT has no trigger in Make, so nothing in SUMIT starts a scenario by itself. You start the scenario another way: with a trigger from another app, such as a form or a store, or with the schedule on the first module, set to every 15 minutes by default. If that other app has an instant trigger, the SUMIT modules run as soon as it fires. Every SUMIT module then acts on the bundles that trigger hands over, one operation per module and per bundle.
04What if a SUMIT module is missing in Make?
Use Make an API Call. It calls any endpoint of the SUMIT API with the same connection, which covers what the 8 listed modules leave out. Make's documentation for SUMIT is marked as limited and gives no field list, so the Run once button is the quickest way to see what each module expects and returns. When the answer looks wrong, the Make troubleshooting guide on this site walks through reading a failed run step by step.
05Is Make or n8n better for SUMIT?
It depends on the tool your team already uses. On the Make side, the facts are clear: 8 action modules, no trigger, a generic connection and Make an API Call for the rest. The same app may also exist as an n8n node, so compare the coverage you need in each tool rather than the brand, and pick the editor you are comfortable building and maintaining scenarios in. Both tools can call an API directly when a dedicated module or node is missing.
Same platform

Other docs you might need on this stack.

Browse all integrations