Resources · Make integration

BotDistrikt Make integrationAutomate BotDistrikt with Make.

Can your BotDistrikt chatbot talk to the rest of your tools without code? The BotDistrikt Make integration gives you 17 modules: 1 trigger, 13 actions and 3 searches. This page is for teams that run the bot and want a clear path to a first working scenario.

Try the BotDistrikt integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the BotDistrikt Make integration do?

The BotDistrikt Make integration links your BotDistrikt account to Make, a visual tool where you build a scenario: the automation itself, a chain of modules. Each module is one brick, such as a trigger, an action or a search, and together they move BotDistrikt users, responses and broadcasts to and from your other apps.

Keep user profiles in sync. When a lead comes in from a form or a shop, Upsert a User creates the BotDistrikt profile or refreshes it if it already exists, and Add User Attributes stores extra details on it. Search Users then finds that person again later in the flow.

Send the right message at the right moment. Send a Reply answers one person, while Create a Broadcast prepares a message for many. Cancel a Broadcast is the safety net when a campaign should stop before it goes out.

Manage canned responses from outside the bot. Create a Response, Update a Response and Search Responses let a content team edit the bot's answers from a spreadsheet or a ticketing tool instead of opening the builder each time.

Be aware of one gap: Make's own documentation for BotDistrikt is limited, because little public information exists about the app. Module fields are shown in the editor once your connection works, so explore them there. If a listed module does not cover your need, Make an API Call reaches the rest of the API. For a broader look at the platform, read our Make review, and if you are weighing tools, the n8n vs Make comparison lays out the criteria. When a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect BotDistrikt to Make?

  1. 01

    Add a BotDistrikt module

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

  2. 02

    Name it and authorize Make

    Give the connection a clear name if you like, for example the bot or client it belongs to. Then either approve Make on the BotDistrikt page that opens, or paste the key BotDistrikt gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now read your account, so the fields fill with lists it pulls from BotDistrikt. If the panel stays empty, the connection did not go through and needs to be created again.

First scenario

Your first scenario with BotDistrikt

GoalWhen BotDistrikt reports a new webhook event, Make creates or refreshes the matching user with Upsert a User.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario. The editor opens on an empty canvas with a single +: that is where the first module goes.

  2. 02

    Place the trigger

    Click the +, search for BotDistrikt and pick Watch Webhook Events. Select the connection you created, or click Create a connection if this is your first BotDistrikt module.

  3. 03

    Add Upsert a User

    Click the + on the right of the trigger and add Upsert a User. Map the data received from the trigger into its fields, so each event updates the right profile instead of creating duplicates.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows, above each module, the bundles it received. A bundle is one item passed along, here one event, then one user.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

What starts a BotDistrikt scenario

1 module starts a scenario when something happens in BotDistrikt. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by BotDistrikt as soon as it happens.

BotDistrikt1Watch Webhook Events

Watch Webhook Events

triggerIn the docs only

Watch Webhook Events is the only BotDistrikt trigger, so it is how a scenario reacts to what happens in your bot without you pressing a button. Each event it picks up becomes a bundle for the next modules.

How it fires
scheduled, Make checks the app on the scenario's schedule. Its type is inferred from its name, as no detailed listing exists: despite the word webhook, check the badge in the editor (a clock means scheduled).
When to use it
any flow that should follow the bot's activity, such as logging new conversations in a sheet or refreshing a CRM contact.
Watch out
the documentation does not list which events come through, so run it once and read the bundle before you map anything.
Modules

What you can do with BotDistrikt in Make

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

BotDistrikt1

Add User Attributes

ActionIn the docs only

Add User Attributes enriches a BotDistrikt profile with extra details coming from another tool, so the bot knows more about the person it talks to. It works on one user per run.

When to use it
after a purchase or a form submission, when you want the new information attached to the existing profile rather than a fresh record.
Watch out
the documentation does not name the attributes, so check the list Make shows once connected.
BotDistrikt2

Cancel a Broadcast

ActionIn the docs only

Cancel a Broadcast stops a mass message you already set up in BotDistrikt, which gives you an emergency brake driven by data from elsewhere. It acts on one broadcast at a time.

When to use it
when a promotion sells out or an event is called off and the planned message would now be wrong.
Watch out
you need the broadcast to cancel, so keep the value returned by Create a Broadcast in your flow.
BotDistrikt3

Create a Broadcast

ActionIn the docs only

Create a Broadcast prepares a message for many BotDistrikt users at once, straight from a scenario, so a campaign can start from your calendar tool or your shop instead of the bot builder.

When to use it
when a new product goes live or an announcement is approved in another app and your audience should hear about it through the bot.
Watch out
test with Run once on a small audience first, since a broadcast reaches many people.
BotDistrikt4

Create a Response

ActionIn the docs only

Create a Response adds a new answer to your BotDistrikt bot from outside the builder, which lets people who never open the bot settings still contribute content.

When to use it
when your support team approves a new answer in a shared document or a helpdesk and wants it live in the bot without copying it by hand.
Watch out
run Search Responses before it, or you may add a second answer for the same question.
BotDistrikt5

Delete User Attributes

ActionIn the docs only

Delete User Attributes removes details stored on a BotDistrikt profile, which keeps the data about each person clean and current. It is the counterpart of Add User Attributes.

When to use it
when a customer unsubscribes, changes plan or asks for part of their data to be erased, and the old attribute would mislead the bot.
Watch out
a deletion cannot be undone from Make, so filter carefully before this module.
BotDistrikt6

Finish a Webhook

ActionIn the docs only

Judging by its name, Finish a Webhook tells BotDistrikt that your scenario has done its part in a webhook exchange. Place it after the modules that do the real work.

When to use it
in a scenario started by Watch Webhook Events, once the data has been processed and the bot should move on.
Watch out
the documentation says nothing about what it sends back, so read its output after a test run.
BotDistrikt7

Make an API Call

ActionIn the docs only

Make an API Call gives you access to any part of the BotDistrikt API that the other listed modules do not cover, using the same connection. It is the fallback when a ready-made module is missing.

When to use it
when you know the endpoint you need from BotDistrikt's API reference and no listed module does the job.
Watch out
you write the request yourself, path and body included, so this module asks for more technical comfort than the others.
BotDistrikt8

Replay a Message

ActionIn the docs only

Replay a Message sends a message from your BotDistrikt bot again, which saves you from rebuilding content that already exists. The name points to reusing a message, not writing a new one.

When to use it
when a user comes back after a silence, or a step in another tool shows they missed an earlier message.
Watch out
the documentation gives no detail on this module, so try it on a test user and check the result in the bot.
BotDistrikt9

Search Responses

SearchIn the docs only

Search Responses looks through the answers stored in your BotDistrikt bot and hands back what it finds, so the next modules can check or edit them. A search can return zero, one or several bundles.

When to use it
before Create a Response or Update a Response, to know whether the answer already exists.
Watch out
when several results come back, each one runs the following modules, which uses more operations on your plan.
BotDistrikt10

Search Users

SearchIn the docs only

Search Users finds people in your BotDistrikt audience so you can act on their profile in the next step. It is the simple search, handy when you already know who you are looking for.

When to use it
when an order or a ticket arrives in another app and you need the matching bot user before sending a reply.
Watch out
no result is a normal outcome, so add a filter that handles the empty case.
BotDistrikt11

Search Users (Advanced)

SearchIn the docs only

Search Users (Advanced) gives you a more precise way to pull a group of BotDistrikt users, useful when a simple lookup is too broad. Its name points to more criteria than Search Users.

When to use it
when you build a segment, for example to update several profiles or to check who should receive a broadcast.
Watch out
each user returned is one bundle and one run of the following modules, so a large segment adds up quickly in operations.
BotDistrikt12

Send a Reply

ActionIn the docs only

Send a Reply lets your scenario answer one BotDistrikt user directly, with a message built from data in your other tools. It is the one-to-one counterpart of Create a Broadcast.

When to use it
when an order ships, a booking is confirmed or a ticket is closed elsewhere, and the person should hear it in the chat.
Watch out
you need to know which user to answer, so place Search Users or the trigger data before this module.
BotDistrikt13

Update a Response

ActionIn the docs only

Update a Response edits an answer that already exists in your BotDistrikt bot, so a change of price, address or opening hours reaches the chat without anyone touching the builder.

When to use it
when the source of truth lives in a sheet or a CMS and the bot should stay aligned with it.
Watch out
the module needs to know which answer to change, so find it first with Search Responses.
BotDistrikt14

Update a User

ActionIn the docs only

Update a User changes the profile of someone who is already in BotDistrikt, which keeps the bot's view of that person in step with your CRM or shop.

When to use it
when you are sure the user exists, for instance right after Search Users returned them.
Watch out
if the person may not exist yet, prefer Upsert a User, which avoids a failed run when the profile is missing.
BotDistrikt15

Upload Media

ActionIn the docs only

Upload Media sends a file into BotDistrikt from another app, so images or documents stored elsewhere become available to your bot. It saves the manual download and upload.

When to use it
when a new product photo or a brochure lands in cloud storage and the bot should be able to share it.
Watch out
on the Free plan Make handles files up to 5 MB, so larger media need a paid plan.
BotDistrikt16

Upsert a User

ActionIn the docs only

Upsert a User creates a BotDistrikt profile when the person is new and updates it when they already exist, all in one module. That removes the need for a search followed by two branches.

When to use it
when contacts arrive from a form, a shop or a CRM and you cannot know in advance whether the bot has met them.
Watch out
map the identifying value consistently, or the same person may end up with two profiles.
Need help

Need help automating BotDistrikt with Make?

A person reads every message.

FAQ

Common questions about BotDistrikt and Make

01Is the BotDistrikt Make integration free?
Yes, BotDistrikt is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle, so a busy bot uses more of them. The price of BotDistrikt itself is a separate matter.
02What does it take to connect BotDistrikt to Make?
A BotDistrikt account and a Make account are enough to start. Make's documentation for this app lists no prerequisites and no specific connection steps, so the generic flow applies. Add any BotDistrikt module, click Create a connection, name it if you want, then either approve Make on the BotDistrikt page or paste the key the app provides, and click Save. Having admin rights on the bot makes that step easier. Once saved, the connection is reused by all 17 BotDistrikt modules in every scenario you build.
03Does the BotDistrikt trigger in Make react in real time?
No. Watch Webhook Events is classed as a scheduled trigger, a type inferred from its name since no detailed listing exists. Make checks BotDistrikt on the scenario's schedule instead of being called the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. If your use case needs a faster reaction, set the shortest interval your plan allows and keep in mind that each check counts toward your usage.
04What if a BotDistrikt module is missing in Make?
Use Make an API Call. It reaches any endpoint of the BotDistrikt API from your scenario with the same connection, so you are not limited to the other listed modules. You will need BotDistrikt's API reference to know the path and the body to send. Also note that Make's own documentation for this app is limited because little public information exists, so the fields of each module are best discovered in the editor after connecting. Running the scenario once and reading the bundles is the quickest way to learn what each module returns.
05Make or n8n for BotDistrikt: which one fits?
It depends on your criteria, not on a winner. Many apps also have an n8n node, so check whether BotDistrikt does and whether the actions you need exist on both sides before you decide. On Make you get 17 modules, including a scheduled trigger and a generic API call, plus a visual editor where each module shows the bundles it received. Compare the modules each tool offers for your bot, the way you prefer to build, and how usage is counted in each. The comparison page linked above in this guide walks through those criteria in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations