Run Make scenarios from your bot
The Make scenario power-up lets your bot run one of your Make scenarios during a chat, such as adding a lead to your CRM, creating a support ticket or looking up an order. The bot fills in the scenario's inputs from the conversation and gets back whatever the scenario returns.
Add one power-up for each scenario you want the bot to run.
Before you start
- Who can do this: team owners and admins.
- A Make account on any plan, including Free. Scenario inputs, scenario outputs and on-demand scheduling are available on every plan.
- A scenario that is active and scheduled to run On demand. Only on-demand scenarios can be started by your bot.
- Scenario inputs defined on the scenario for anything the bot should send, such as an email address. To get results back, end the scenario with a Return output module and define its outputs.
- A Make API token. In Make, open your profile, go to API access and add a token with the
organizations:read,scenarios:read,scenarios:writeandscenarios:runscopes. Make requires all three scenario scopes to run a scenario through its API. - Your Make zone, which is the start of your Make dashboard address (for example
eu1.make.comorus2.make.com).
Steps
- Open your bot, go to the Power-ups tab and click New power-up.
- Choose Make scenario and click Create power-up.
- Under Make account, choose your team's Make account. If none is connected yet, click Connect Make account, choose your Zone, paste your token into API token and click Connect. Chat Thing checks the token with Make before saving it.
- Choose the scenario in Make scenario. Only on-demand scenarios appear. Inactive ones are marked "(inactive)".
- Check the Power-up name and Description. They're filled in from the scenario, but the description is how the bot decides when to run it, so say what the scenario does and when to use it, for example "Add the visitor to our CRM once they've shared their name and email".
- Configure the Scenario inputs (see below).
- Click Save.
You connect a Make account once per team. Every Make scenario power-up, on any of your team's bots, can use it, so for your next scenario just add another power-up and choose the same account. To use scenarios from another Make account or zone, click Connect another account.
Replace your API token
Your API token is stored encrypted and never shown again after you connect. To change it, for example when it expires:
- Open Connections from the sidebar.
- Under Connected services, find Make and click Replace token.
- Paste the new token and click Replace token.
Every power-up that uses the account switches to the new token. You can also click Replace API token under Make account in a power-up's settings.
To stop all of them using the account, click Disconnect instead. Power-ups that used it stop working until you choose another account in their settings.
Scenario inputs
When you choose a scenario, its inputs are listed in a table:
| Column | What it's for |
|---|---|
| Name | The input's name in Make. |
| Description | Tells the bot what the input is for. It starts with the description from Make. This is how the bot learns to fill it in, so make it clear. |
| Value | Optional fixed value that's always sent, for example the source of a lead. Leave blank to let the bot fill it in or ask the visitor. |
| Ignore | The bot never sends this input. Use it for optional inputs you don't need. Required inputs can't be ignored. |
If you change the scenario's inputs in Make, click Refresh inputs from Make. Your descriptions, values and ignore choices are kept for inputs that still exist.
Check it works
- Chat with your bot while signed in and ask it to do what the scenario does.
- Open View details on the power-up call to see the inputs the bot sent and the outputs or error Make returned.
- Check the scenario's history in Make, and the result in the target app.
Limits
- The bot waits up to 40 seconds for the scenario to finish. A scenario that takes longer still runs in Make, but the bot doesn't get its outputs and tells the visitor it's still running.
- Each run uses operations from your Make plan. If your Make organization runs out, the bot reports that the scenario couldn't run.
Troubleshooting
My scenario doesn't appear in the list
Check that its schedule is set to On demand, that you chose the Make account it belongs to, and that the account uses the zone your organization is hosted in. If Make reports a missing scope when you connect, create a token with organizations:read, scenarios:read, scenarios:write and scenarios:run.
The bot says the scenario couldn't run
Open View details on the power-up call. Make's message usually names the problem, such as a missing required input or a scenario that isn't active. Turn the scenario on in Make, or improve the input Descriptions so the bot collects what's needed.
The bot says the Make account was disconnected or the token can't be read
The account was disconnected on the Connections page, or its token needs replacing. Connect the account again, or replace its token, then choose it under Make account in the power-up's settings and click Save.
The scenario runs but the bot doesn't get a result
Add a Return output module at the end of the scenario and define its outputs. Without it, the bot only learns that the scenario ran.
Related
- Call your API from your bot
Let your bot call any HTTP API to look up or send data, such as order status, stock levels or new leads, using the API request power-up.
- Trigger Zapier actions from your bot
Use the Zapier AI Action power-up to let your bot run actions you've set up in Zapier. Zapier has deprecated AI Actions, so read this first.
Last updated