Make

Make is an automation platform that connects hundreds of apps through “scenarios”. Make was formerly called Integromat, and the integration works the same way under either name. Uncanny Automator connects to it in both directions: the Send data to Make webhook action passes data from a recipe into a Make scenario, and the Receive data from Make webhook trigger starts a recipe when a Make scenario sends data to your site. No account connection is needed inside Uncanny Automator; the two sides are linked by webhook URLs.

The action is in the free plugin. The trigger requires Uncanny Automator Pro.

Send data from a recipe to Make

In this direction a Make scenario waits for data from your WordPress site. You create the scenario first, so that Make gives you the address to send data to, then build the recipe.

Create the Make scenario

1. In Make, click Create a new scenario. Make’s own guide is at Creating a scenario.
2. Choose Webhooks as the first module, and in its Triggers section choose Custom webhook.
3. Click Add, give the webhook a name, and click Save. Make starts listening for data straight away.
4. Click Copy address to clipboard. This is the URL your recipe will send to.

You do not need to define a data structure in Make. It learns the structure from the first request your recipe sends.

Add the action to the recipe

1. Open the recipe at Automator > Recipes, or create one from Automator > Add new recipe, and add its trigger (see Creating a recipe).
2. Click Add action, or the + at the end of the flow. In the picker, type Make in the search box and select Make, then Send data to Make webhook.
3. In the Set up step, paste the address you copied from Make into URL.
4. Request method opens on POST; keep it. The Data format field below it is set to x-www-form-urlencoded. Make’s custom webhook accepts that format and JSON, so leave it unless your scenario needs something specific.
5. Leave Authorization empty, and keep the Headers row the action adds (Accept, application/json) as it is. Fill in Authorization or add headers only if your scenario requires them. Authorization takes an authorization string that is added to the request header and masked once you save. To add a header, click Add header and fill in its Name and Value.
6. In Body, click Add pair for each piece of data to send. Key is the label Make will see, Data type is the type of the value (Text for names and email addresses), and Value is the data. For dynamic data, click the ∗ button at the end of the Value field and pick a token: common tokens such as the user’s first name are available in every recipe, and trigger tokens such as a course title come from the recipe’s triggers. The token appears in the field as a chip with its name, such as User first name.

To send nested data, write the key as a path with a forward slash between the levels, for example user/email and user/name, and set Data format to JSON. The field’s own hint says the same: “Separate keys with / to build nested data.” Make then receives a user object with email and name inside it.

7. Click Test. The Test step offers two tests: Validate data format, which is optional and shows the exact payload the action will send without sending it, and Send webhook, which sends a real request to the URL. Run Send webhook; when Make answers, the test shows Test passed. Token values are not replaced during a test, so the placeholders arrive in Make as written. See Testing triggers and actions.
8. Click Save changes. To skip the test, click Save without testing instead; the action still runs normally.
9. Make sure the action and the trigger are On, then switch Recipe on in the top bar.

Finish the scenario in Make

Back in Make, the webhook module reports that it has received data (from your test, or from the first real run) and shows the fields it found. Click OK and build the rest of the scenario, mapping the keys you sent onto the modules that follow. Make keeps the structure it learned; if you add keys to the Body later, send another test so that Make picks them up.

Start a recipe from Make

In this direction Uncanny Automator waits for data from Make. The trigger runs for anyone, not for a logged-in user, so it goes in a recipe for Everyone; see Recipes for Everyone. It requires Uncanny Automator Pro.

1. Go to Automator > Add new recipe, select Everyone, and click Confirm.
2. Click Add trigger. In the picker, search for Make, select it, then select Receive data from Make webhook. The trigger carries a Pro label.
3. The Set up step shows the recipe’s Webhook URL. Click the copy button at the end of the field; the URL is unique to this recipe and accepts PUT, GET and POST requests.

4. In your Make scenario, add the HTTP module Make a request. Paste the recipe’s Webhook URL into URL, set Method to POST and Body content type to application/JSON, and enter the data in the body as a Data structure or a JSON string.
5. Back in the trigger, click Test, then Listen for webhook. The test listens for one minute, with a countdown and a Stop listening button. Run the Make scenario once so that it sends a request. When the request arrives, the test shows Test passed and a table of the keys and values it received.
6. Click Use these fields and confirm with Use these fields. The builder returns to the Set up step with a row in Fields for each key received; those rows become the trigger’s tokens. Click Save. If you cannot send a sample yet, click Back to setting up fields, fill in the Fields table by hand instead (Key, Type, and Sample value for each key Make will send; Add pair adds a row), and click Save.

Important: The test listens only while the recipe is off. Finish the test before you switch Recipe on.

Nested data from Make arrives with the same slash notation: a user object with an email inside it becomes the key user/email. Add the actions that should run for each request; because this is an Everyone recipe, actions that need a user get one through the Run actions as card between the triggers and the actions. Switch Recipe on when the recipe is ready. For the trigger’s data formats and more examples, see Webhook triggers.

Related: Send data to a webhook, Webhook triggers, Testing triggers and actions, Recipes for Everyone