Resources · Make integration

SlimCRM Make integrationAutomate SlimCRM with Make.

Can Make keep SlimCRM in step with the rest of your tools? The SlimCRM Make integration gives you 52 modules: 7 triggers, 29 actions and 16 searches. This guide shows sales and ops teams how to link the account and build a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SlimCRM Make integration do for you?

The SlimCRM Make integration links your SlimCRM account to Make, a no-code tool where you build a scenario: an automation made of modules chained one after the other. A module is a single brick, either a trigger that starts the run, an action that writes in SlimCRM, or a search that finds records. You choose the bricks and Make runs them for you.

No lead left without a next step. Watch Lead picks up leads from SlimCRM and Create a Task puts a follow-up on a salesperson's list, so nobody has to remember to call back.

Invoices your bookkeeper sees without asking. Watch Invoice hands each invoice it finds to the next module, which can add it to a spreadsheet or post it in a team channel, with no numbers copied by hand.

A new hire ready on day one. When Watch Staff picks up a new team member, Create a Task lines up their first onboarding steps in SlimCRM, so nothing depends on someone remembering.

What Make does not do here: none of the 7 triggers is instant, so every run waits for the scenario's schedule, every 15 minutes by default. The official documentation lists the modules without describing them, so test each one with Run once before relying on it. For anything the list misses, Make an API Call reaches the SlimCRM API with the same connection.

Weighing your options? The n8n vs Make comparison puts the two tools side by side. If the editor is new to you, Make training walks through it, and Make troubleshooting helps when a run fails.

Connect

How do you connect SlimCRM to Make?

  1. 01

    Add a SlimCRM module

    Open a scenario in Make, add any SlimCRM module and click Create a connection. A connection is your SlimCRM account linked to Make once; every SlimCRM module you add later reuses it.

  2. 02

    Name the connection

    In the Connection name field, type a label you will recognize later, such as the team that owns the account. The field is optional, but a clear name saves guesswork once several accounts are linked.

  3. 03

    Paste your API token

    Enter the API token you generated in SlimCRM, or follow the on-screen instructions, then confirm. Once the connection exists, the module can list the SlimCRM data it is able to read.

First scenario

Your first scenario: a follow-up task for every new lead

GoalWhen Watch Lead finds a lead in SlimCRM, Make creates a follow-up task for it in SlimCRM.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to place the first module, the trigger.

  2. 02

    Add Watch Lead

    Search for SlimCRM, pick Watch Lead and click Create a connection to paste your API token. This scheduled trigger now opens the flow.

  3. 03

    Add Create a Task

    Click the + on the right of Watch Lead and choose Create a Task. Fill its fields by mapping the lead data Watch Lead passes along, so each task names the right prospect.

  4. 04

    Test with Run once

    Add a test lead in SlimCRM, then click Run once. Read the bundles each module received and open SlimCRM to check that the task looks the way you expect.

  5. 05

    Schedule and switch on

    On the clock of Watch Lead, keep the default of every 15 minutes or choose another interval your plan allows, then switch the scenario on. New leads now arrive with a task attached.

Triggers

What can start a SlimCRM scenario?

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

SlimCRM1Watch Contact

Watch Contact

triggerIn the docs only

Watch Contact keeps an eye on the contacts in your SlimCRM account and starts the scenario with each one it picks up, passed along as a bundle, meaning one item the next module can work with.

How it fires
scheduled: Make checks SlimCRM on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan.
When to use it
copying people into a newsletter tool or a shared address book once the next check finds them.
Watch out
the documentation does not say which contacts it returns, so click Run once and read the bundles before building on it.
SlimCRM2Watch Expense

Watch Expense

triggerIn the docs only

Watch Expense brings each expense recorded in SlimCRM into Make, so spending stops living in a single place and can reach the people who approve or book it.

How it fires
scheduled: Make polls SlimCRM on the scenario's timing, which is why the module shows a clock badge.
When to use it
an office manager logs a purchase and the finance spreadsheet should show it without retyping.
Watch out
every module after the trigger runs once per expense, and each run is an operation, the unit Make counts on your plan, so a busy account spends operations faster than a quiet one.
SlimCRM3Watch Invoice

Watch Invoice

triggerIn the docs only

Watch Invoice hands every invoice it finds in SlimCRM to the rest of your scenario, ready to be copied into a spreadsheet, a message or another app.

How it fires
scheduled: Make checks SlimCRM on the scenario's schedule rather than hearing from SlimCRM directly.
When to use it
letting the person who chases payments know an invoice exists without opening SlimCRM.
Watch out
with the default schedule an invoice can wait up to 15 minutes before Make notices it; on a paid plan the interval can drop to 1 minute if timing matters to your billing.
SlimCRM4Watch Lead

Watch Lead

triggerIn the docs only

Watch Lead is the natural starting point for sales automations: it catches leads in SlimCRM and gives each one to the next module as its own bundle.

How it fires
scheduled: Make asks SlimCRM for leads at each run of the scenario's schedule, so nothing reaches Make between two checks.
When to use it
a lead should become a call task, an alert in the sales channel or a row in a pipeline sheet.
Watch out
a test on an empty account gives the next modules nothing to work with, so create a sample lead in SlimCRM before you click Run once.
SlimCRM5Watch Payment

Watch Payment

triggerIn the docs only

Watch Payment tells your scenario about payments recorded in SlimCRM, turning each one into a bundle that other modules can thank, file or report on.

How it fires
scheduled: Make checks SlimCRM on the scenario's schedule, set on the clock of this first module.
When to use it
sending a thank-you email to the client or updating a cash tracking sheet as soon as the next check sees the payment.
Watch out
if you run Watch Invoice and Watch Payment in two separate scenarios, both count against the 2 active scenarios of the Free plan.
SlimCRM6Watch Staff

Watch Staff

triggerIn the docs only

Watch Staff follows the team members stored in SlimCRM and starts a run for each one it picks up, which makes it the entry point for onboarding flows.

How it fires
scheduled: Make polls SlimCRM on the scenario's schedule, every 15 minutes unless you change the clock.
When to use it
a new colleague appears in SlimCRM and their tool accounts, welcome message and first tasks should follow.
Watch out
staff records describe your own people, not clients, so send their details only to tools your team is allowed to use for personal data.
SlimCRM7Watch Task

Watch Task

triggerIn the docs only

Watch Task picks up tasks from SlimCRM and pushes each one into the scenario, so to-dos can travel to a calendar, a chat or a project board.

How it fires
scheduled: Make checks SlimCRM on the scenario's schedule instead of being notified when someone adds a task.
When to use it
a team that plans its day in another tool still wants SlimCRM tasks to show up there.
Watch out
placing Create a Task later in the same scenario can bring the created tasks back through Watch Task on the next check and start a loop; send new tasks elsewhere or split the flow.
Modules

What can SlimCRM do inside a scenario?

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

SlimCRM1

Search Tasks

SearchIn the docs only

Search Tasks returns the SlimCRM tasks that match what you ask for, whether that is zero, one or many, each one as its own bundle for the next module.

When to use it
before a scenario adds a task, to check whether a follow-up already exists for that client.
Watch out
when nothing matches, the modules after it receive nothing and stay idle, so plan what the empty case should mean.
SlimCRM2

Create a Client

ActionIn the docs only

Adding a client to SlimCRM from any other tool becomes a single step: the new record appears in your account with the data you map into the module.

When to use it
a signed quote or a won deal in another app should turn into a SlimCRM client without retyping.
Watch out
the documentation says nothing about duplicate checks, so place Search Clients by Keyword in front of it.
SlimCRM3

Create a Lead

ActionIn the docs only

Create a Lead drops a fresh prospect into SlimCRM, so contact forms and event sign-up lists feed your pipeline directly instead of an inbox.

When to use it
someone fills in the form on your website and sales should see the lead in SlimCRM right after the scenario runs.
Watch out
a form submitted twice gives two leads; Search Leads by Keyword placed before it lets you spot the repeat.
SlimCRM4

Create a Payment

ActionIn the docs only

Money received elsewhere gets written into SlimCRM with this module, which keeps the client file complete for whoever opens it next.

When to use it
your payment provider or banking app confirms a transfer and the account manager needs to see it where they work.
Watch out
a payment recorded twice skews your figures and has to be removed with Delete a Payment, so test with Run once on a sample first.
SlimCRM5

Create a Staff

ActionIn the docs only

Create a Staff opens a team member's record in SlimCRM from information you already hold in another tool, such as an HR form or a signed contract.

When to use it
a new hire should exist in SlimCRM before their first assignment, without anyone keying their details twice.
Watch out
staff records carry personal data, so map only what SlimCRM needs and keep the connection in trusted hands.
SlimCRM6

Create a Task

ActionIn the docs only

Turning an event into a to-do is the whole job here: the module writes a task into SlimCRM with the text and details you map from earlier modules.

When to use it
a new lead, a late invoice or a support email should leave a clear next step for someone on the team.
Watch out
combined with Watch Task in the same scenario, the tasks it creates can start the flow again.
SlimCRM7

Create an Expense

ActionIn the docs only

Create an Expense logs a cost in SlimCRM from a receipt, a card notification or a purchase approved in another app, so spending is recorded where the client work lives.

When to use it
an employee submits a claim through a form and finance wants it in SlimCRM without copying amounts by hand.
Watch out
check the first expense created by Run once in SlimCRM itself, since a wrong mapping repeats on every run.
SlimCRM8

Create an Invoice

ActionIn the docs only

Create an Invoice produces a SlimCRM invoice from data gathered earlier in the scenario, so billing starts from the event that justifies it.

When to use it
a project is marked finished in your project tool and the client should be billed without anyone rebuilding the invoice.
Watch out
an invoice is a document your clients may see, so test on a dummy client with Run once before switching on.
SlimCRM9

Delete a Client

ActionIn the docs only

Delete a Client removes a client from SlimCRM for good: none of the 52 modules brings a deleted record back.

When to use it
a data deletion request arrives through a form and the record has to go from every tool in the same run.
Watch out
point it at the right record by mapping the client from a search or a Get a Client module; a wrong mapping deletes someone else.
SlimCRM10

Delete a Lead

ActionIn the docs only

Clearing out a dead prospect takes one module: Delete a Lead erases the lead you point it to and keeps the pipeline free of noise.

When to use it
a lead flagged as spam in your form tool should vanish from SlimCRM too.
Watch out
never place it right after a search that can return many bundles unless you really mean to delete every one of them.
SlimCRM11

Delete a Payment

ActionIn the docs only

Delete a Payment takes a payment entry out of SlimCRM, which is how a scenario undoes a record that should never have been logged.

When to use it
a transfer was refunded or cancelled in your payment tool and SlimCRM should no longer count it.
Watch out
no SlimCRM module restores a deleted payment, so run it only on payments identified through Get a Payment or Search Payments.
SlimCRM12

Delete a Staff

ActionIn the docs only

When someone leaves the team, Delete a Staff takes their record out of SlimCRM in the same flow that closes their other accounts.

When to use it
an offboarding checklist in another tool reaches its last step and SlimCRM should match it.
Watch out
the documentation does not say what happens to work linked to that person, so review their tasks and clients in SlimCRM first.
SlimCRM13

Delete a Task

ActionIn the docs only

Delete a Task removes a to-do from SlimCRM, handy when the reason for it disappears somewhere else and the list should stay honest.

When to use it
a meeting is cancelled in your calendar and the preparation task created for it should go too.
Watch out
target the task through List Tasks or Search Tasks, and try the scenario on a throwaway task with Run once.
SlimCRM14

Delete an Expense

ActionIn the docs only

Delete an Expense wipes an expense line from SlimCRM so your totals match reality again after a mistake or a rejected claim.

When to use it
a claim is turned down in your approval tool and the cost should disappear from SlimCRM at the same moment.
Watch out
if another tool has already copied the expense, deleting it in SlimCRM does not undo that copy.
SlimCRM15

Delete an Invoice

ActionIn the docs only

Delete an Invoice takes an invoice out of SlimCRM entirely, useful for cleaning up after tests or after an invoice was raised on the wrong client.

When to use it
a trial scenario created sample invoices and you want your billing view clean again.
Watch out
no module restores a deleted invoice, so read it with Get an Invoice first and check the bundle before you switch on.
SlimCRM16

Get a Client

ActionIn the docs only

Get a Client fetches the full record of one client, so later modules can use every detail SlimCRM holds on that person or company.

When to use it
a scenario starts from an invoice or a task, and the email you send needs the client's details too.
Watch out
it returns a single client; to work on several, reach for List Clients or one of the client searches.
SlimCRM17

Get a Lead

ActionIn the docs only

Get a Lead reads a single lead from SlimCRM so the next modules work with its complete, current record rather than an older copy.

When to use it
before sending a lead to your email tool, to be sure you pass on the latest version.
Watch out
you have to tell it which lead to read, usually by mapping it from a trigger or a search placed earlier.
SlimCRM18

Get a Payment

ActionIn the docs only

Need the details of one payment in the middle of a scenario? Get a Payment returns that payment as a bundle the next modules can quote.

When to use it
a thank-you message or a receipt stored in another app should refer to the payment it concerns.
Watch out
it only reads, so testing it with Run once changes nothing in SlimCRM, though each run still costs an operation.
SlimCRM19

Get a Staff

ActionIn the docs only

Get a Staff returns one team member's record from SlimCRM, useful whenever a scenario needs to know who a piece of work concerns.

When to use it
a scenario handles a task and you want to notify the colleague concerned by name in your team chat.
Watch out
staff data is personal, so pass on only the details the next tool really needs.
SlimCRM20

Get a Task

ActionIn the docs only

Get a Task pulls one task from SlimCRM with everything it holds, so a report or a message can describe it properly.

When to use it
an email reply mentions a task and you want its current details before the scenario answers or files anything.
Watch out
it handles one task at a time; for all the tasks of a client, List Tasks or Search Tasks fit better.
SlimCRM21

Get an Expense

ActionIn the docs only

Get an Expense reads one expense line from SlimCRM so you can hand its details to the approval or accounting tool that needs them.

When to use it
an approver wants the full picture of a claim before signing it off in another app.
Watch out
it needs to know which expense you mean; map it from Watch Expense or Search Expenses rather than typing it.
SlimCRM22

Get an Invoice

ActionIn the docs only

Get an Invoice brings back one SlimCRM invoice as it stands right now, handy just before you send a reminder or file a copy.

When to use it
a reminder scenario wants to be sure the invoice still matches what the client is asked to pay.
Watch out
reading the invoice right before acting avoids working on an outdated copy handed down from an earlier module.
SlimCRM23

List Clients

SearchIn the docs only

List Clients returns your SlimCRM clients as a stream of bundles, one per client, for every job that needs the whole base at once.

When to use it
loading the client list into a spreadsheet or a mailing tool as a one-off import.
Watch out
each module after it runs once per client, so a large base consumes operations quickly.
SlimCRM24

List Expenses

SearchIn the docs only

List Expenses hands over the expense lines stored in SlimCRM, one bundle each, ready to land in a spreadsheet or a report.

When to use it
an accountant asks for the recorded expenses in a sheet they can sort and annotate.
Watch out
unlike Search Expenses, the module name suggests no narrowing down, so expect the full list and size the next steps for it.
SlimCRM25

List Invoices

SearchIn the docs only

With List Invoices, every SlimCRM invoice becomes a bundle you can copy, count or send on to another tool.

When to use it
building a billing sheet for the finance team, or checking which invoices exist before a batch of reminders.
Watch out
a run on the Free plan stops after 5 minutes, so a very long list processed module after module may not finish in one pass.
SlimCRM26

List Leads

SearchIn the docs only

List Leads pulls the leads from SlimCRM into the scenario, the way to go when a whole pipeline has to be moved or reviewed.

When to use it
you adopt a new email tool and want the current leads loaded into it once.
Watch out
each lead that goes through a later module costs an operation, so check what your plan has left before running it on a full pipeline.
SlimCRM27

List Payments

SearchIn the docs only

List Payments returns the payments recorded in SlimCRM, one bundle per payment, so you can export or review them elsewhere.

When to use it
a manager wants payments mirrored in a spreadsheet to follow the cash coming in.
Watch out
the module only supplies the items; adding them up needs an aggregator, a Make tool that groups bundles, placed after it.
SlimCRM28

List Staffs

SearchIn the docs only

List Staffs gives you the whole team as SlimCRM knows it, one bundle per person, ready to be copied into a directory.

When to use it
keeping a staff directory in a spreadsheet or an intranet page aligned with SlimCRM.
Watch out
former colleagues who still have a record will appear too, so pair your offboarding flow with Delete a Staff to keep the list honest.
SlimCRM29

List Tasks

SearchIn the docs only

List Tasks brings back SlimCRM tasks in bulk, the quickest way to feed a board or a shared summary outside SlimCRM.

When to use it
moving existing tasks into a project tool when a team switches over.
Watch out
it is not a trigger for new tasks; for that, Watch Task at the start of the scenario is the module you want.
SlimCRM30

Make an API Call

ActionIn the docs only

Make an API Call is the way out when the list falls short: it sends a request of your choice to the SlimCRM API with the connection you already set up.

When to use it
you need an endpoint that none of the 52 listed modules covers.
Watch out
you write the request yourself, so you need to know which endpoint to call and what it expects; the module does not guess.
SlimCRM31

Search Clients by Criteria

SearchIn the docs only

Search Clients by Criteria finds the clients that match conditions you set and returns each match as its own bundle.

When to use it
sending a message only to clients who fit a certain profile, rather than to the whole base.
Watch out
the documentation does not list the available criteria; open the module once connected and Make shows what it can read.
SlimCRM32

Search Clients by Keyword

SearchIn the docs only

Search Clients by Keyword looks for clients from a word or a name, the quick answer to the question of whether a client already exists.

When to use it
right before Create a Client, so a returning customer does not get a second record.
Watch out
a short keyword can match several clients; decide in advance what the next modules do with more than one result.
SlimCRM33

Search Expenses

SearchIn the docs only

Search Expenses narrows SlimCRM's expense lines down to the ones that match your request, one bundle per match.

When to use it
a claim arrives from a form and you want to know whether the same cost has already been logged.
Watch out
zero results means the next modules get nothing, which suits a duplicate check but can surprise you in a report.
SlimCRM34

Search Invoices

SearchIn the docs only

Search Invoices finds the SlimCRM invoices that match what you look for, returning one bundle for each invoice found.

When to use it
a client writes to support about a bill and you want the relevant invoices attached to the ticket.
Watch out
several invoices may match, and every one of them goes through the rest of the scenario.
SlimCRM35

Search Leads by Criteria

SearchIn the docs only

Search Leads by Criteria picks out the leads that meet the conditions you choose, so you work on a slice of the pipeline rather than all of it.

When to use it
handing a specific group of leads to a colleague or to a sequence in your email tool.
Watch out
the documentation does not name the criteria, so look at what the module offers once connected and confirm the result with Run once.
SlimCRM36

Search Leads by Keyword

SearchIn the docs only

Search Leads by Keyword finds leads from a word, a name or a company you type or map into the module.

When to use it
an email lands from someone new and you want to know whether they are already a lead before creating one.
Watch out
map the keyword from the incoming data rather than typing it, otherwise every run searches for the same thing.
SlimCRM37

Search Payments

SearchIn the docs only

Search Payments tracks down the payments in SlimCRM that match your search, each one returned as a bundle.

When to use it
a client says they have paid and your support scenario should check SlimCRM before replying.
Watch out
an empty result does not prove the payment never happened, only that SlimCRM holds no matching record yet.
SlimCRM38

Search Staffs by Keyword

SearchIn the docs only

Search Staffs by Keyword finds team members from a name or a word, so a scenario can route work to the right person.

When to use it
an incoming request names a colleague and you want their SlimCRM record before creating a task for them.
Watch out
two colleagues can share a first name, so map a more specific keyword whenever you can.
SlimCRM39

Update a Client

ActionIn the docs only

Update a Client rewrites details on a client that already exists in SlimCRM, so a change made in another tool reaches your CRM too.

When to use it
a client edits their details in a customer portal or a form and SlimCRM should follow.
Watch out
find the client first with Search Clients by Keyword or Get a Client, since the update needs to know which record to touch.
SlimCRM40

Update a Lead

ActionIn the docs only

Update a Lead keeps a prospect's record current as new information comes in from your other tools.

When to use it
a lead books a demo in your scheduling app and the SlimCRM record should reflect that step.
Watch out
the update applies whatever you map, so an empty value could overwrite useful data; check the result in SlimCRM after Run once.
SlimCRM41

Update a Payment

ActionIn the docs only

Update a Payment corrects a payment already recorded in SlimCRM, one per run, without deleting it and starting over, so the history your team relies on stays in one place.

When to use it
after Watch Payment spots a new entry that needs a follow-up change, or when a record from another app shows the payment details were entered wrong.
Watch out
the module needs to know which payment to change, so put Search Payments or Get a Payment upstream and map the result.
SlimCRM42

Update a Staff

ActionIn the docs only

Update a Staff keeps an existing team member's record in SlimCRM in line with what changed elsewhere, so nobody edits the same person twice by hand.

When to use it
your HR tool or an onboarding form registers a change for an employee, and SlimCRM should reflect it too.
Watch out
Search Staffs by Keyword can return several bundles, so check you update the right person before you turn the scenario on.
SlimCRM43

Update a Task

ActionIn the docs only

Update a Task moves one existing SlimCRM task forward from another tool, so you stop switching tabs every time work progresses elsewhere.

When to use it
a ticket closes in your support tool or a form answer arrives, and the matching task in SlimCRM should change as a result.
Watch out
pair it with Search Tasks or Get a Task first, then click Run once on a test task to confirm the right one changes.
SlimCRM44

Update an Expense

ActionIn the docs only

Update an Expense fixes or completes one existing expense line in SlimCRM, so your cost tracking stays accurate without anyone retyping entries.

When to use it
Watch Expense picks up a new expense and a later step, such as an approval in another app, should change it.
Watch out
each update counts as an operation on your plan, so filter out expenses that need no change before this step.
SlimCRM45

Update an Invoice

ActionIn the docs only

Update an Invoice brings one existing SlimCRM invoice up to date from another tool, so billing data matches what your client actually agreed to.

When to use it
a payment lands through Watch Payment, or your accounting app reports a change, and the related invoice should follow.
Watch out
Search Invoices may find more than one match; add a filter or use Get an Invoice so the update never hits the wrong document.
Need help

Need help automating SlimCRM with Make?

A person reads every message.

FAQ

SlimCRM and Make: common questions

01Is the SlimCRM Make integration free?
Yes. SlimCRM is a standard app in Make, so its 52 modules work on the Free plan. That plan allows 2 active scenarios, runs a scheduled scenario at most every 15 minutes, stops each run after 5 minutes, and handles files up to 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and count usage in credits per month. Your SlimCRM account still needs API access, which is a separate matter from Make.
02What do you need to connect SlimCRM to Make?
An active SlimCRM account with API access enabled and a valid API token. In SlimCRM, the token is created under System, Settings, API Management, with the Add Account button, and each token expires on a date its creator chooses. In Make, add any SlimCRM module, click Create a connection, give it a name if you like and paste the token. If API Management does not show up in your account, SlimCRM support can activate the API feature for you.
03Do SlimCRM triggers fire in real time in Make?
No. All 7 SlimCRM triggers are scheduled: Make checks SlimCRM on the scenario's schedule instead of being called the moment something changes. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan, while paid plans go down to 1 minute. None of the triggers is instant, so there is no webhook to create. For follow-ups such as a task after a new lead, this pace is usually enough.
04What if a SlimCRM module is missing in Make?
Use Make an API Call. It reuses your SlimCRM connection and can reach any endpoint of the SlimCRM API, so the 52 listed modules are not a ceiling. You do need to know which endpoint to call and what it expects. Also keep in mind that Make's documentation page for SlimCRM warns that its content is AI-generated from SlimCRM's own documentation and may contain errors, so verify important details and contact SlimCRM directly when a behavior surprises you.
05Make or n8n for SlimCRM?
It depends on the tool your team already works in and the modules you need. In Make, SlimCRM comes with 52 modules, split into 7 scheduled triggers, 29 actions and 16 searches, plus Make an API Call for the rest, and it is open to the Free plan. n8n often offers a node for the same apps, so check whether one exists for SlimCRM before you decide. Compare both on the exact operations your process needs; the n8n vs Make comparison linked earlier covers the wider differences.