Make.com + Sapience – Sapience Cloud

Walkthrough of connecting Sapience to Make.com

💡

This guide is a hands-on tutorial teaching you how to wire up Sapience to work with a Make.com automation. If you are looking for the detailed docs for the underlying system, find those here:

Sapience HTTP Tools for Web Hooks

Overview

In this tutorial we are going to learn about Sapience’s HTTP tools, and how you can use them with any automation platform.

In this flow we are going to use Make.com, but you could use this with Zapier, n8n, Power Automate, IFTT, or any 3rd party integration platform that you currently use.

The only hard requirement for this flow is that the other tool be able to expose a webhook (which most do).

Walkthrough Part 1: Create an automation in Make

Steps:

create a new scenario in make

make the 1st node a webhook

copy the webhook URL that make.com creates - like in this screenshot (its blacked out, but you would grab/copy/save yours)

A tip for best results, you can use the dynamic redertmine data structure feature of the webhook, but for more deterministic control, open advanced settings and specify your own data structure. This makes all the variables really clear.

Here’s the window for defining a data structure on a Make.com webhook.

Creating a custom data structure in a Make.com web-hook. This is highly recommended for all your Make.com flows, not just when working with Sapience.

Alternatively, you can use Make.com’s scenario inputs - this is also a good way to structure your automation:

Build out whatever automation you want to build as you normally would do in Make.com. Test it as you normally would.

Here is us testing the web hook we created:

You can see that it FAILED when we went to the webhook address. That’s great. That’s because we didn’t provide the required data and we marked this as required.

💡

Note on working with AI: putting in strict rules for required data items and good descriptions is good practice when you’re working with humans, but when you’re workign with AI its vital. In this case, Sapience would hit the webhook, see this useful validation error, and then “fix itself” on the next call it makes.

So, now we resubmit, putting the proper data on the querystring:

Note that in this stage we are still just testing within Make.com, nothing to do with Sapience.

You can see in the red highlighted box that we are now giving the Make.com scenario the required data as querystring parameters, which starts with the ?, and each key=value pair are separated by the & symbol.

You can build any automation you like, that returns data or not. You can use all of Make.com’s features. Just make sure that if you want to return data it will execute and return within the 3 minute max timeout.

*In this* *make.com* *scenario, it listens on the webhook URL, and then adds a row to Google Sheets whenever a properly shaped call to the web-hook happens.*

So, after we did the test runs in the browser, here is what our Google Sheet looks like this:

So, that’s great. We’ve completed Part 1: Building an automation. Let’s see how to use it in Sapience.

Part 2: Using External Automations In Sapience

Sapience using hook: Now, lets go over to Sapience and tell it to use it with a regular prompt. Here’s a screenshot of what we did, and the actual prompt is below. Note that this is all using the build-in global Sapience Agent. But the same technique applies to any other agents that have the HTTP TOOLs feature turned on.

Here’s the prompt we used:

ok - use your http_get tool to call this make.com webhook. https://[YOUR-OWN-MAKE-WEBHOOK-URL-HERE]?taskName=task3&notes=notes3. You should replace the test data values with some real data to try it out and tell me what you get back

3. Sapience thinks for a second, and then gets to work:

*Here you can see that Sapience quickly figures out the data shape format for the webhook, and calls it succesfully. It then reports back to you on what happened.*

Next, lets go and look at our Google Sheet and see what we can see…

*Our Google sheet, now with real/useful data in it from Sapience!!*

ITS ALIVE!!!! 🙂

Congrats! Let’s Recap:

You did it! If you were following along with this, then at this stage you have actually done something really cool. Lets break it down:

You created an automation (if this is your first, congratulations!)

You got Sapience talking to an external system

You got Sapience triggering your automation intelligently, passing real data to it

You just unlocked the world of getting Sapience to drive all your other systems with external automations

Ideas For More:

Here are some ideas for what you can do:

Have Sapience save data to Google Sheets or Google Docs

Have Sapience analyze files and notes internally, and then write it to external systems

Have Sapience do work for you, then deliver it to a client workspace