Make

Connect Make and Expertise can work with your automations directly: list scenarios, explain what one does, run it on demand, check why a run failed, and read or write data store records. Reads are instant; running, activating, or deleting anything pauses for your approval first.

What you can ask

“What scenarios do I have, and which ones are active?”

“Explain what my ‘New Lead → CRM’ scenario does.”

“Run the invoice-sync scenario now.” (asks for approval before running)

“Why did last night’s scenario run fail?”

“Retry that failed execution.” (asks for approval before running)

Connecting

Open Connections in the dashboard and click Make → Connect.
Enter your Base URL, the zone your Make account lives in, like https://us2.make.com or https://eu1.make.com (visible in your browser address bar when you’re logged into Make).
In Make, create an API token under Profile → API, then paste it in.
Ask Expertise to list your Make scenarios to confirm it’s live.

A Make API token only works in the zone it was created in. If your Base URL is eu1.make.com, create the token there too, a token from us2 won’t authenticate.

Tools

Tool	What it does	Approval
`make_list_organizations`	List your Make organizations and their teams.	–
`make_list_teams`	List the teams in an organization.	–
`make_list_scenarios`	List scenarios for a team, with active state and scheduling.	–
`make_get_scenario`	Fetch one scenario’s details.	–
`make_get_scenario_blueprint`	See a scenario’s module flow, to explain what it does.	–
`make_run_scenario`	Run a scenario on demand.	Required
`make_activate_scenario`	Turn on a scenario’s schedule or triggers.	Required
`make_deactivate_scenario`	Turn off a scenario’s schedule or triggers.	Required
`make_update_scenario`	Rename a scenario, move it, or change its scheduling.	Required
`make_delete_scenario`	Delete a scenario.	Required
`make_list_scenario_executions`	List a scenario’s run history.	–
`make_get_execution`	Get one run’s status, outputs, and failing step.	–
`make_list_incomplete_executions`	List failed runs parked for manual resolution.	–
`make_retry_incomplete_execution`	Retry a failed run.	Required
`make_list_hooks`	List a team’s webhooks and the scenarios they trigger.	–
`make_list_data_stores`	List a team’s data stores.	–
`make_list_data_store_records`	Browse records in a data store.	–
`make_create_data_structure`	Define a field schema for a new data store.	Required
`make_create_data_store`	Create a data store.	Required
`make_create_data_store_record`	Add a record to a data store.	Required
`make_update_data_store_record`	Edit a record in a data store.	Required
`make_delete_data_store_records`	Delete records from a data store.	Required

Good to know

Running a scenario runs everything in it. A scenario can send emails, message people, or write to other systems, Expertise reads its name and flow first so it can tell you what will happen before you approve.
Scenarios must be active to run. If a run request fails because the scenario is off, Expertise will say so rather than guessing why.
Deletes are permanent, a scenario or data store record removed this way can’t be recovered.
Every write pauses for your approval, including activating or deactivating a scenario’s live schedule.

Troubleshooting

A request fails saying the token is missing a scope

API token scopes are set when you create the token in Make under Profile → API, check the token includes the scope for what you asked (for example scenarios:run to run scenarios).

Expertise can't find a scenario you know exists

Scenarios belong to a specific team, ask Expertise to list your organizations and teams first, then list scenarios for the right one.

Getting started

Connections

CRM

Sales & prospecting

Email & messaging

Calendar & meetings

Docs, files & data

Project & dev tools

Support & community

Billing & analytics

Automation

Expertise platform

What you can ask

Connecting

Tools

Good to know

Troubleshooting

​What you can ask

​Connecting

​Tools

​Good to know

​Troubleshooting

What you can ask

Connecting

Tools

Good to know

Troubleshooting