Resources · Make integration

myCRMSIM Make integrationAutomate myCRMSIM with Make.

What happens to a message that lands in myCRMSIM while nobody is looking? The myCRMSIM Make integration gives you 1 trigger and 2 actions to catch inbound messages and answer them. This page walks you through the connection and a first working scenario.

Try the myCRMSIM integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the myCRMSIM Make integration do for you?

The myCRMSIM Make integration links your myCRMSIM account to Make, so messages can move without copy and paste. You build a scenario, which is the automation itself: a chain of modules, where each module is one brick such as a trigger or an action. myCRMSIM brings 3 modules to that chain.

Nobody misses an incoming message. Watch new inbound message picks up each new message on the scenario's schedule, and Send a message passes it on to the person who should handle it. That is the scenario built step by step further down.

Replies go out from other tools. Start the flow from another app, a form or a spreadsheet row for instance, and let Send a message deliver the text through myCRMSIM. The 123FormBuilder Make integration shows what such a starting point looks like.

Anything the list does not cover. Make an API call reaches any endpoint of the myCRMSIM API with the connection you already have, which helps given how short the module list is.

Know the limits before you start: Make's own documentation says it cannot fully document myCRMSIM, because too little public information exists about the app. Expect to test each module with Run once rather than rely on a field reference. The same app may also exist as an n8n node; the n8n vs Make page lays out how the two tools differ, and the Make training covers the editor from scratch.

Connect

How do you connect myCRMSIM to Make?

  1. 01

    Add a myCRMSIM module

    In your scenario, add any myCRMSIM module and click Create a connection. A connection is your myCRMSIM account linked to Make once; every myCRMSIM module of your scenarios reuses it afterwards.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, which is optional but handy with several accounts. Then either authorize Make on the myCRMSIM page that opens, or paste the key myCRMSIM gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. The connection now appears in the module's dropdown, and you can fill the rest of the module. If Make can read lists from your account, it offers them there instead of asking you to type values.

First scenario

Build your first scenario with myCRMSIM

GoalWhen a new inbound message reaches myCRMSIM, Make sends a message to the colleague in charge.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor to place the first module.

  2. 02

    Place the trigger

    Search for myCRMSIM, pick Watch new inbound message and select the connection you created, or click Create a connection if you skipped that part.

  3. 03

    Add Send a message

    Click the + on the right of the trigger and choose Send a message. Map the text of the inbound message into it, and set the colleague who should receive it.

  4. 04

    Test with Run once

    Send a test message to your myCRMSIM account, then click Run once. Open the bubble above each module to read the bundle, meaning the single message, it received.

  5. 05

    Schedule and switch on

    Click the clock on the trigger to set how often Make checks, every 15 minutes by default, then switch the scenario on. It now runs by itself.

Triggers

What starts a myCRMSIM scenario

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

myCRMSIM1Watch new inbound message

Watch new inbound message

triggerIn the docs only

This trigger gives your scenario a starting point each time a message comes into myCRMSIM, so the rest of the chain can route or answer it. Each message becomes one bundle for the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, 15 minutes at the shortest on the Free plan. The type comes from the module's name, as the doc does not describe it, so look for the clock badge.
When to use it
whenever an incoming message should reach a person or another tool without someone watching the inbox.
Modules

What the myCRMSIM modules do

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

myCRMSIM1

Make an API call

ActionIn the docs only

With this action you reach any endpoint of the myCRMSIM API from your scenario, and you keep the connection you already set up, so there is no second login to manage.

When to use it
the moment you need something the two other modules do not offer.
Watch out
the doc gives no endpoint list for myCRMSIM, so you need the API reference from myCRMSIM itself.
myCRMSIM2

Send a message

ActionIn the docs only

Here is the action that lets your scenario speak: it sends a message through your myCRMSIM account, filled with data mapped from earlier modules.

When to use it
to pass an inbound message on to a colleague, or to answer an event that happened in another app.
Watch out
Run once really sends, so point your tests at your own contact first.
Need help

Need help automating myCRMSIM with Make?

A person reads every message.

FAQ

myCRMSIM and Make: frequent questions

01Is the myCRMSIM Make integration free?
Yes, myCRMSIM is a standard app, so it works on the Free plan of Make. That plan gives you 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Every module run on one bundle counts as one operation, the unit Make deducts from your plan. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. The price of myCRMSIM itself is a separate matter between you and myCRMSIM.
02What do you need to connect myCRMSIM to Make?
A myCRMSIM account and a Make account. The Make documentation lists no other prerequisite. You add a myCRMSIM module, click Create a connection, optionally name it, then authorize Make on the myCRMSIM page or paste the key the app provides, and save. The connection is created once and reused by every myCRMSIM module afterwards. Since Make describes its own myCRMSIM documentation as limited, keep your account details at hand in case the window asks for something unexpected.
03Does the myCRMSIM trigger in Make fire in real time?
No. Watch new inbound message is a scheduled trigger: Make checks myCRMSIM on the scenario's schedule instead of being called by the app. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval, while paid plans go down to 1 minute. A message can therefore wait until the next check before your scenario handles it. Note that the type is inferred from the module's name, as the doc gives no description, so confirm the clock badge in the editor.
04What if a myCRMSIM module is missing in Make?
Use Make an API call. It calls any endpoint of the myCRMSIM API with the connection you already have, so an operation missing from the list can still run inside the scenario. You will need the myCRMSIM API reference to know which endpoint to call, since Make says its documentation of the app is incomplete for lack of public information. Test the call with Run once and read the bundle it returns before you map its output into the next module.
05Should you use Make or n8n for myCRMSIM?
It depends on the tool your team already works in. On the Make side, myCRMSIM offers 3 modules: one scheduled trigger for inbound messages, Send a message, and Make an API call for everything else. The same app may also have an n8n node, which you would check on the n8n side. Neither tool is ranked here: compare the available operations for your use case, and pick the one where your other automations already live, so your whole setup stays in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations