Resources · Make integration

SilFer Bots Make integrationAutomate SilFer Bots with Make.

Can your chatbot talk to the rest of your tools without a developer? The SilFer Bots Make integration gives you 21 modules: 12 triggers, 8 actions and 1 search. This guide connects your account and walks you through a first scenario that wins back abandoned carts.

Try the SilFer Bots integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SilFer Bots Make integration automate?

The SilFer Bots Make integration links your bot account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. For SilFer Bots, Make offers 21 modules that follow your bot's users, tags, sequences, chats and orders, and act back on them.

Bring shoppers back. Watch Cart Abandoned picks up carts left behind, and Send Flow to User opens the right conversation with that person. It is the first scenario built further down this page.

Let tags drive your other tools. When Watch New Tagged User sees a «VIP» or «demo booked» tag, a CRM or mailing tool can update the same person. Watch Tag Removed From User covers the reverse move.

Keep orders honest. A payment app confirms a charge, and Mark Order as Paid updates the order inside SilFer Bots, so nobody retypes it.

Know the limits before you start. Make's documentation for SilFer Bots is thin: it names the modules without describing them, so the notes below read each one from its name, and your first Run once is where you confirm what it returns. There is no Make an API Call module either. To weigh the tool itself, read the Make review or the n8n vs Make comparison, and if you want to learn to build faster, see Make training.

Connect

How do you connect SilFer Bots to Make?

  1. 01

    Add a SilFer Bots module

    In a scenario, add any SilFer Bots module and click Create a connection. A connection is your SilFer Bots account linked to Make once, then reused by every SilFer Bots module you add later.

  2. 02

    Name it and authorize

    Give the connection a name if you run several bots, it helps later. Then either approve Make on the SilFer Bots page that opens, or paste the key SilFer Bots gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The module now shows your connection, and Make can list what it reads from your account when you fill the fields. If the lists stay empty, the connection is the first thing to recheck.

First scenario

Your first scenario: follow up on an abandoned cart

GoalWhen a cart is abandoned in SilFer Bots, Make sends that shopper a flow to bring them back.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. The empty canvas shows a large +: click it to add the first module, the one that starts everything.

  2. 02

    Pick the trigger

    Search for SilFer Bots and choose Watch Cart Abandoned. Click Create a connection to link your account, or pick the connection you already saved.

  3. 03

    Add the action

    Click the + on the right of the trigger and choose Send Flow to User. Fill its fields, then map the shopper from the trigger's bundle, the item Make passes from one module to the next.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open what each module received and make sure the flow went to the person who left the cart, not to someone else.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Keep it or shorten it on a paid plan, then switch the scenario on.

Triggers

What can start a SilFer Bots scenario?

12 modules start a scenario when something happens in SilFer Bots. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SilFer Bots as soon as it happens.

SilFer Bots1Watch New or Updated Custom Field

Watch New or Updated Custom Field

triggerIn the docs only

You get a scenario that reacts when a user's custom field in SilFer Bots receives a value or a new one, going by the module's name. Each changed field reaches Make as a bundle, one item handed to the next module.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule, every 15 minutes by default.
When to use it
your bot asks for a phone number or a delivery city, and a spreadsheet or CRM should hold the same answer.
Watch out
new and updated values arrive through the same trigger, so decide in the next module whether an update may overwrite what you stored.
SilFer Bots2Watch Order Concluded

Watch Order Concluded

triggerIn the docs only

Finished sales can flow straight into your back office. As its name says, this trigger starts the scenario when an order in SilFer Bots is concluded, and the order arrives as a bundle later modules can read.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule, so a concluded order waits for the next check.
When to use it
invoices, delivery notes or a thank-you message should go out once the sale is closed, not when it starts.
Watch out
Watch New Order sits earlier in the same story. Pick the moment you need and avoid wiring both to the same action.
SilFer Bots3Watch Tag Removed From User

Watch Tag Removed From User

triggerIn the docs only

This one tells your other tools that someone has left a segment. It picks up users whose tag was removed in SilFer Bots, judging by its name, so a list or campaign elsewhere can drop them too.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule rather than hearing about it on the spot.
When to use it
a lead loses the «interested» tag after going quiet, and your email tool should stop writing to them.
Watch out
a scenario that runs Remove Tag from User and another that watches removals can keep feeding each other, so keep their tags apart.
SilFer Bots4Watch Cart Abandoned

Watch Cart Abandoned

triggerIn the docs only

Shoppers who stopped halfway become a second chance. Going by its name, the trigger starts a scenario each time SilFer Bots records an abandoned cart, with that cart handed over as a bundle.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule, every 15 minutes unless you change it.
When to use it
a shop that sells through its bot wants a reminder flow sent to people who left items behind.
Watch out
one check can return several carts, and each one runs the next modules. Every run costs operations, the unit Make counts on your plan.
SilFer Bots5Watch Live Chat Disabled

Watch Live Chat Disabled

triggerIn the docs only

Here you learn when a conversation leaves live chat. The module catches users whose live chat was switched off in SilFer Bots, as its name suggests, which is useful for logging how a support exchange ended.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule, so the news can land one interval after the fact.
When to use it
close the matching ticket in a helpdesk or send a short satisfaction question once the agent is done.
Watch out
that delay makes it a poor fit for anything the user expects to see immediately.
SilFer Bots6Watch Live Chat Enabled

Watch Live Chat Enabled

triggerIn the docs only

Your team hears about users who switched to live chat. The trigger, named for exactly that, picks up users whose live chat was turned on in SilFer Bots and passes each one to the rest of the scenario.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule, not the second a user asks.
When to use it
post a message in your team chat so an agent picks the conversation up.
Watch out
on the Free plan the shortest interval is 15 minutes, a long wait for someone asking for help. Paid plans go down to 1 minute.
SilFer Bots7Watch New Order

Watch New Order

triggerIn the docs only

Every order taken by your bot can land in the tools that handle it. As its name says, this trigger starts the scenario for each new order SilFer Bots records, before any later stage of that order.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule and brings back the orders found since the last check.
When to use it
a shop wants each bot order copied to a spreadsheet or an order sheet for the warehouse.
Watch out
the documentation doesn't describe what an order bundle contains, so run a Run once on a real order before you map fields.
SilFer Bots8Watch New Tagged User

Watch New Tagged User

triggerIn the docs only

The tags you already set in your bot turn into switches for other apps. Judging by its name, the trigger starts the scenario when a user receives a tag in SilFer Bots.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule and returns the users tagged since the previous run.
When to use it
people tagged «VIP» or «demo booked» should enter a CRM pipeline or a mailing list.
Watch out
if the same scenario also runs Add Tag to User on the watched tag, the next check picks up its own work and the scenario starts over. Watch one tag, add another.
SilFer Bots9Watch New User

Watch New User

triggerIn the docs only

Each newcomer to your bot can reach your contact lists without a copy and paste. Going by the name, the trigger starts the scenario for every new user SilFer Bots records.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule, so users gather between checks and arrive together.
When to use it
marketing wants every new bot subscriber in the CRM or a sheet, without copying them by hand.
Watch out
every user is a bundle and runs the following modules, so a busy bot uses more operations. Check the count after your first test.
SilFer Bots10Watch New “Trigger Integromat” Event

Watch New “Trigger Integromat” Event

triggerIn the docs only

Your bot gets to decide exactly when Make steps in. The module's name points to a «Trigger Integromat» event raised from SilFer Bots, which suggests a step you place in a conversation to start a scenario on purpose.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule for new events of that kind.
When to use it
a precise point of a conversation, such as the end of a quiz, should send data to Make.
Watch out
the documentation doesn't explain how to set up that event on the SilFer Bots side, so confirm it with a test before building on it.
SilFer Bots11Watch User Added to Sequence

Watch User Added to Sequence

triggerIn the docs only

Your follow-up campaigns become visible outside the bot. This trigger starts the scenario when a user joins a sequence in SilFer Bots, going by the module's name, and hands that user to the next module.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule and collects the users added since the last run.
When to use it
record in the CRM who entered an onboarding sequence, so sales don't send the same messages twice.
Watch out
this only covers the entry. Pair it with Watch User Removed From Sequence if the exit matters too.
SilFer Bots12Watch User Removed From Sequence

Watch User Removed From Sequence

triggerIn the docs only

Records elsewhere stay correct when a sequence stops for someone. The trigger picks up users taken out of a sequence in SilFer Bots, as its name indicates.

How it fires
scheduled, Make checks SilFer Bots on the scenario's schedule, so the removal is seen at the next check.
When to use it
update a lead status or pause a parallel email campaign when someone leaves a bot sequence.
Watch out
between the removal and that check, another tool may still send a message. On a paid plan, a shorter interval narrows that gap.
Modules

What can Make do in SilFer Bots?

SilFer Bots gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SilFer Bots1

Add Tag to User

ActionIn the docs only

Any other app can now sort people inside your bot. The action adds a tag to one user in SilFer Bots, so a purchase, a form or a CRM change places that person in the right segment.

When to use it
a payment confirmed in another tool should give the buyer a «customer» tag.
Watch out
the new tag also wakes any scenario running Watch New Tagged User on it.
SilFer Bots2

Clear User Custom Field

ActionIn the docs only

Stale data disappears from a user's profile. This action empties one custom field for one user in SilFer Bots, so the bot stops relying on an answer that no longer holds.

When to use it
an address changed in your CRM, or a one-off answer should be asked again later.
Watch out
clearing is not rewriting. When a new value exists, Set Custom Field is the right module.
SilFer Bots3

Create New Contact

ActionIn the docs only

People met outside the bot end up in it. As its name says, the action creates a contact in SilFer Bots from data another module brings in, such as a form entry.

When to use it
leads captured on a landing page should also exist in your bot so it can reach them.
Watch out
the documentation doesn't say what happens when the contact already exists. Test with a known person before switching on.
SilFer Bots4

Find User by ID

SearchIn the docs only

You get a user's record when all you hold is their identifier. This search looks up a user in SilFer Bots by ID and hands what it finds to the next modules.

When to use it
another app sends a SilFer Bots user ID and a later step needs details on that person.
Watch out
a search can return zero, one or several items. Plan for the empty case so the next action doesn't fail.
SilFer Bots5

Mark Order as Paid

ActionIn the docs only

Orders in your bot match your real payments without manual updates. The action marks an order in SilFer Bots as paid once another tool confirms the money arrived.

When to use it
a payment platform validates a transaction and the bot's order should reflect it right after.
Watch out
check which order the mapping targets during Run once. A wrong mapping marks someone else's order as paid.
SilFer Bots6

Remove Tag from User

ActionIn the docs only

Someone leaves a segment automatically when things change elsewhere. The action takes one tag off one user in SilFer Bots, so your bot stops treating them as part of that group.

When to use it
a refund or a cancelled subscription means the buyer should lose the «customer» tag.
Watch out
a scenario built on Watch Tag Removed From User will see the change, so check the two don't trigger each other.
SilFer Bots7

Send Flow to User

ActionIn the docs only

A whole bot conversation opens from Make. Judging by the name, the action sends one of your SilFer Bots flows to a user, so the bot takes over from there with the messages you prepared.

When to use it
an abandoned cart, a confirmed booking or a closed ticket should start the matching conversation.
Watch out
the user sees the flow as soon as it's sent, so run your first test on your own profile.
SilFer Bots8

Send Text Message to User

ActionIn the docs only

A single message reaches a user without building a flow. The action sends a text to one user of your SilFer Bots bot, with content you can fill from earlier modules.

When to use it
a short notice such as a shipping update, where a full flow would be too much.
Watch out
personalise the text with mapped data. A fixed message sent to every bundle quickly reads like spam.
SilFer Bots9

Set Custom Field

ActionIn the docs only

Your bot remembers data that lives in other tools. The action writes a value into a custom field of a SilFer Bots user, so later conversations can use it.

When to use it
a lead score, a plan name or a loyalty status from your CRM should be available to the bot.
Watch out
it writes over the current value. Use Clear User Custom Field when the field should end up empty.
Need help

Need help automating SilFer Bots with Make?

A person reads every message.

FAQ

SilFer Bots and Make: common questions

01Is the SilFer Bots Make integration free?
Yes, SilFer Bots is a standard app in Make, so it works on the Free plan. That plan comes with limits: 2 active scenarios, at least 15 minutes between two 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module and per bundle. This page gives no price for SilFer Bots itself.
02What do you need to connect SilFer Bots to Make?
A SilFer Bots account and a Make account. Make's documentation lists no prerequisite for this app, so the standard steps apply: add a SilFer Bots module, click Create a connection, name it if you like, then either approve Make on the SilFer Bots page or paste the key the app gives you, and click Save. The documentation doesn't say which of those two methods SilFer Bots uses, and the connection window will show it. Once saved, the connection serves every SilFer Bots module in all your scenarios.
03Do SilFer Bots triggers in Make run in real time?
No. The 12 SilFer Bots triggers are scheduled: Make checks the app on the scenario's schedule instead of being called through a webhook. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan, and paid plans go down to 1 minute. For live chat requests that delay matters, so choose the shortest interval your plan allows. None is listed as an instant trigger, the kind an app calls the moment something happens. That type is read from the module names, so check the clock badge on the module in the editor.
04What if a SilFer Bots module is missing in Make?
You work around it, because this app has no Make an API Call module, the universal module some apps offer for requests Make hasn't packaged. The documentation is limited too: it names the 21 modules without describing them. Two routes remain. Build the step with another app's module when the data also lives there, or ask the team at the agency to study your case. Before that, run Run once on the modules that exist, since one of them may already return what you need.
05Should you use Make or n8n for SilFer Bots?
It depends on what each tool actually offers for this app. On Make, SilFer Bots comes with 21 modules available from the Free plan, and this page walks you through a first scenario. For n8n, the sources behind this page don't confirm a dedicated SilFer Bots node, so check its catalogue before choosing. The n8n vs Make comparison linked earlier sets the two tools side by side on general criteria. The practical rule is simple: go where the SilFer Bots modules you need exist.
Same platform

Other docs you might need on this stack.

Browse all integrations