Resources · Make integration

DeepKeep Make integrationAutomate DeepKeep with Make.

Want DeepKeep checks inside your automations? The DeepKeep Make integration gives you 3 action modules and no trigger. This guide is for teams already using DeepKeep: connect the account, place the modules after another app, and test before going live.

Try the DeepKeep integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DeepKeep Make integration do?

The DeepKeep Make integration links your DeepKeep account to Make, a no-code tool where you build a scenario: a chain of modules that runs by itself. DeepKeep brings 3 action modules, Check input, Create conversation and Make API call, that you place after data coming from another app.

Start with the simplest use: send text received elsewhere to DeepKeep before anything else happens. A form, a chat app or a spreadsheet row feeds the scenario, and the Check input module hands that text to DeepKeep, which, going by the module's name, checks it. Each module is a brick of the scenario, and each item it handles is a bundle.

A second path is opening a conversation in DeepKeep from an event in another tool, with the Create conversation module. A third is the Make API call module, listed as an action by Make, for requests the two other modules do not cover.

Be clear about the limits. Make's own documentation for DeepKeep is marked as limited: there is no official description of the modules, no list of fields and no documented connection steps. Plan to discover the fields in the editor once your connection exists, and read the output of each test. The Make troubleshooting guide helps when a run fails.

DeepKeep has no trigger, so a scenario always starts with another app or with a schedule. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and Make training covers the editor from zero.

Connect

How do you connect DeepKeep to Make?

  1. 01

    Add a DeepKeep module

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

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps once you have several accounts or workspaces. Pick something your teammates will recognize, such as the team or the environment it belongs to.

  3. 03

    Authorize and save

    Depending on what the window asks, authorize Make on the DeepKeep page or paste the key DeepKeep gives you. Then click Save. The module fields load once the connection exists.

First scenario

Build your first scenario with DeepKeep

GoalWhen a new message arrives in another app, Make sends its text to DeepKeep with Check input, then opens a DeepKeep conversation.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Choose the app where your messages arrive as the first module, since DeepKeep has no trigger of its own.

  2. 02

    Add Check input

    Click the + on the right of the first module, search for DeepKeep and pick Check input. Create the connection, then map the text coming from the first module into the fields Make shows.

  3. 03

    Add Create conversation

    Add Create conversation after Check input. Fill its fields with data from the earlier modules. Make only lists what it can read once the connection works, so run a test before filling everything.

  4. 04

    Test with Run once

    Click Run once. The scenario runs one time, and you can open each module to read the bundles it received and returned. Since no field is documented, this output is your best guide.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What the DeepKeep modules do

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

DeepKeep1

Check input

ActionIn the docs only

Going by its name, this module has DeepKeep check an input before the rest of your scenario uses it. Make gives no official description, so read the result of a first test to see exactly what comes back.

When to use it
right after the module that brings in text from a form, a chat or a spreadsheet.
Watch out
no field is documented, so map one value, click Run once and inspect the bundle before adding filters.
DeepKeep2

Create conversation

ActionIn the docs only

Going by its name, it opens a new conversation in DeepKeep from data your scenario already holds, so an event in another tool starts a DeepKeep exchange without anyone doing it by hand.

When to use it
when each new request, ticket or message in another app should have its own conversation on the DeepKeep side.
Watch out
this is an action, so it runs once per bundle: ten incoming rows mean ten conversations and ten operations.
DeepKeep3

Make API call

ActionIn the docs only

Judging by its name, it lets you send DeepKeep a request that neither Check input nor Create conversation handles. Make lists it as an action but documents nothing about it, so treat it as the option for people comfortable with an API.

When to use it
only after checking that the two other modules cannot do what you need.
Watch out
you will need DeepKeep's own API reference to fill it, since Make's documentation stays silent here.
Need help

Need help automating DeepKeep with Make?

A person reads every message.

FAQ

DeepKeep and Make: frequent questions

01Is the DeepKeep Make integration free?
Yes, DeepKeep is a standard app, so you can use it from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module per bundle. Your DeepKeep subscription itself is a separate matter to check with DeepKeep.
02What do you need to connect DeepKeep to Make?
You need a DeepKeep account and a Make account. Make's documentation lists no specific prerequisite and no dedicated steps for DeepKeep, so the generic flow applies: add a DeepKeep module, click Create a connection, optionally name it, then either authorize Make on the DeepKeep page or paste the key DeepKeep provides, and click Save. If a key is required and you do not have one, ask the person who administers DeepKeep in your organization.
03Does DeepKeep start a Make scenario in real time?
No, because DeepKeep has no trigger module in Make. A scenario that uses it must start elsewhere. You can open it with an instant trigger from another app, which calls Make through a webhook as soon as something happens, or with a scheduled trigger from another app that Make checks on the scenario's schedule. A new scenario runs every 15 minutes by default, and the Free plan does not go below that interval.
04What if a DeepKeep module is missing in Make?
It depends on what you need. The app has only 3 modules: Check input, Create conversation and Make API call. It does not include Make's universal Make an API Call module, and Make's documentation for DeepKeep is marked as limited, so do not expect hidden options. If the modules fall short, look for another app that covers the step, or ask the Hack'celeration team through the help form at the bottom of this page to study your case.
05Should you use Make or n8n for DeepKeep?
It depends on your criteria rather than on a winner. On Make, DeepKeep offers 3 action modules, no trigger and limited documentation, so check that these modules match your use case with a Run once test. The same app often has an n8n node as well: compare the actions each side offers for DeepKeep, the tool your team already uses and who will maintain the scenario. Pick the one where your automation is complete and easy to follow.
Same platform

Other docs you might need on this stack.

Browse all integrations