> This is the Markdown of a Backed Help Centre page, https://admin.backed.giving/help/integrations/make.md. Every page is listed at https://admin.backed.giving/help/llms.txt.

> This page uses Backed's default terms, such as Funding Round and Application Template. An organisation may rename them, so read each as your organisation's own term if you've renamed it.

The Backed app for Make lets a scenario start when something happens in Backed and create or change
records in Backed as one of its modules. It offers exactly what the Zapier app offers, built from
the same definition, so the two change together. [Zapier](zapier.md) explains the parts they share
in more detail.

The app is listed in Make's directory at
[make.com/en/integrations/backed](https://www.make.com/en/integrations/backed) when the listing is
live. The `Make` card on the `Details` tab of `Settings > Profile and terms`, under
`Automation platforms`, links to it.

## What you can automate

- **Instant triggers**, which run the scenario within a minute: `Application submitted`,
  `Application status changed`, `Decision made`, `Milestone submitted`, `Payment paid` and
  `Registration entity created`.
- **Actions:** `Create or update registration entity`, `Add application note`,
  `Set application tags` and `Upload file`.
- **Searches:** `Find application by number` and `Find registration entity by ABN or name`.

## Before you start

Create an API Credential for Make on the `API Access` tab of `Settings > Profile and terms`, with
the write scopes your scenarios' actions need and an Administrator under `Acts as`. The table in
[Zapier](zapier.md#before-you-start) lists the scope each action needs; see also
[API access](api-access.md).

## Connect Backed to Make

1. In Make, add a Backed module to a scenario and select `Add` to create a connection.
2. Enter your organisation's host, such as `yourname.backed.giving`, and the credential's
   `Client ID` and `Client Secret`.
3. Save. Make shows the connection under the credential's name.

## Your first scenario

1. Create a scenario and add the Backed `Decision made` trigger.
2. Choose your connection and create the webhook Make asks for.
3. Add a module for the system that should hear about each decision, map the fields, and turn the
   scenario on.

## What appears on the Webhooks tab

Each Backed trigger webhook becomes an endpoint on the `Webhooks` tab of
`Settings > Profile and terms` with a `Make` badge. An Administrator can disable, enable, test or
delete it there, but not edit it: change the scenario in Make instead. See [Webhooks](webhooks.md).

## When something fails

An action the credential's scopes don't allow fails in Make with a message naming the missing
scope, and changes nothing in Backed. Deleting the credential disables every endpoint it made, so
every scenario using it stops. Records a scenario changes show the credential and its `Acts as`
Administrator in their history. `Upload file` waits about 15 seconds for Backed's malware check;
if the check is still running, the message gives an Upload ID. To recover that one file, stop the
scenario's schedule, run the module once with `Upload ID to resume` set to it, then clear the field
before the scenario runs again: while it is set, every run attaches that same file.
[Zapier](zapier.md#when-something-fails) covers each case.

## Turn it off

Delete the scenario, and its webhook when Make asks, to remove its endpoint from the `Webhooks`
tab. To stop every scenario at once, delete the credential on the `API Access` tab.

## See also

- [Zapier](zapier.md)
- [Webhooks](webhooks.md)
- [API access](api-access.md)
- [Integrations home](integrations-home.md)