N8N + Sapience – Sapience Cloud

Walkthrough of connecting Sapience to N8N

💡

This guide is a hands-on tutorial teaching you how to wire up Sapience to work with a N8N 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 N8N, but you could use this with Make.com, 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 N8N

Steps:

create a new scenario in n8n

make the 1st node a webhook

select HTTP Method - GET or POST.

select production url

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

Tip for best results:define what data you will return. By default, the scenario returns the result of the last node. To change this, select the Respond method “Using Respond to Webhook node” and add this node to your scenario. This makes the results much clearer.

When you add the node, you can also define what should be returned. Even if your workflow does not return any data, it is still good practice to let your agent know that everything completed successfully.

You can use various respond methods, but if you want to return data and clearly inform your agent that everything ran smoothly, it’s best to choose the method shown below.

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

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

In this n8n 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. Make sure you’re using the HTTP tool that matches your webhook method: use http_tool for GET requests and http_post for POST requests.

Here’s the prompt we used:

ok - use your http_get tool to call this n8n webhook. https://[YOUR-OWN-N8N-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…

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