Connecting workflow webhooks to AI: start a workflow from any system
Yes, in both directions. A workflow in IntraGPT can get its own shielded web address: any system that can send a message sets that workflow going. The other way round, the assistant can send a message to another system, provided that system has been approved beforehand. That is how IntraGPT works with software for which no separate connector exists.
What a webhook does in both directions
An address of its own per workflow
Every workflow can get its own web address. Whoever calls that address starts that workflow and no other. You choose the address yourself, so you can make it as inconspicuous as you like.
A key on the door
On that address you put a key. Only a call that sends the right key along starts the workflow; everything else is refused without anything being set in motion.
What comes with the message goes in
Whatever the other system sends along becomes available inside the workflow. A step further on can decide what should happen with this particular message and who hears about it.
Attachments belong with it
A photo or a document may travel with the message. The workflow can read that attachment, summarise it or pass it on, instead of only noting that something was attached.
The assistant reports out itself
The other way round, the assistant sends a message to another system, with or without an attachment. It hears whether the receiver accepted it and can say so in the conversation.
Only towards approved systems
Outbound messages go solely to systems you have approved beforehand. If a destination is not on that list, nothing leaves and the assistant is told so.
What you set in motion with it
E-commerce
- Situation
- A customer fills in the returns form in the webshop and adds a photo of the item.
- What the agent does
- The webshop sends the report to the workflow's address, with the order details and the photo attached.
- Result
- The workflow assesses the report and gets everything ready, so the service desk no longer has to work through a mailbox.
Industry and manufacturing
- Situation
- When a fault occurs, a machine monitor can do precisely one thing: send a message.
- What the agent does
- The monitor calls the shielded address with the key that belongs to it, so the workflow starts immediately.
- Result
- The right engineer gets the report with its context, without a detour through a mailbox.
Customer service
- Situation
- After a call is wrapped up an external system has to be updated for which no separate connector exists.
- What the agent does
- The assistant sends a message to that system, which was put on the list of approved destinations beforehand.
- Result
- It hears whether it was accepted and says so in the conversation, so nobody has to check it afterwards.
Government
- Situation
- An internal reporting system may send outbound traffic to one fixed address and nothing else.
- What the agent does
- That fixed address is the workflow, shielded with a key only the reporting system knows.
- Result
- Reports come in and get handled without anything having to change in that system's security.
From incoming message to handled report
-
1
Connect through the platform
In the workflow designer you give the workflow its own address and put a key on it. You share that key only with the system that may start the workflow.
-
2
Set the permissions
For outbound messages you record which systems are approved. That list is the boundary: whatever is not on it is out of the assistant's reach.
-
3
What the assistant sees
The details sent with a message, including any attachment. Nothing beyond that, and only inside the workflow the message was meant for.
-
4
What gets recorded
Incoming messages and outgoing calls are recorded, including whether the receiver accepted them. A failed call therefore does not vanish quietly.
Why an address on its own is not enough
An inbound address is a door into your environment and an outbound message sends data outside. Both sides therefore have a lock of their own.
Where the data lives: Nederland of de EU
Address plus key
An inconspicuous address is a hurdle, not a lock. With a key on it, every call that fails to send it is refused, wherever it comes from.
Nothing to probe
A call on an address that does not exist yields nothing and sets nothing going. So there is no finding out which workflows exist by simply trying things.
Outbound within the lines
The assistant can only call systems that were approved in advance. Nothing leaves for an address someone tries to slip in along the way.
Confirmation instead of hope
The assistant hears whether the receiver accepted the message and that is recorded. The model also runs on our own server in the Netherlands, and what passes through is never used to train a model.
Questions about workflow webhooks
Does IntraGPT work with webhooks?
Yes, in both directions. A workflow can be started from outside through its own shielded address, and the assistant can send a message to another system itself. For the latter the destination has to be approved in advance.
Can I connect webhooks to ChatGPT?
You can send a message anywhere, but with ChatGPT there is no workflow waiting for it and nowhere to set a key or a list of approved destinations. In IntraGPT the address belongs to a workflow, the key belongs to that address, and outbound traffic is limited to what you approved yourself.
Can anyone call my webhook address?
Without a key the address is the only hurdle, and for anything important that is too little. Put a key on it and every call without that key is refused and the workflow does not start. A call on an address that does not exist yields nothing useful either, so there is no guessing which workflows are there.
What if the system is not on the approved list?
Then nothing goes out and the assistant is told, so it can report that instead of assuming it worked. An administrator adds that destination and it works from then on. The list sits in one place, so it is also immediately clear who may be called at all.
Does this work with n8n?
There is no n8n connector in IntraGPT. What is possible: the assistant sends an outbound message to an external workflow tool, provided that destination was approved in advance. The other way round, such a tool can start a workflow here by calling the shielded address with the right key. Zapier and Make have connectors of their own.
Can I send a file along?
Yes. A photo or a document with the incoming message travels into the workflow and can then be read, summarised or passed on. Outbound the assistant can attach a file too, so a report does not have to stay text only.
How do I know it arrived?
The assistant gets back whether the receiver accepted the message. If something goes wrong or an answer takes too long, it says so in the conversation rather than assuming all is well. Everything going in and out is recorded, so an administrator can check it later.
What does a webhook connection cost?
It belongs to the project we run together. What drives the work is the number of workflows, whether messages also go out and how many destinations have to be approved for that. We make that concrete in a thirty minute call.
How long does setup take?
A workflow with its own address and a key is ready within a quarter of an hour, and you test it with a single message. The real work sits in the workflow behind it: what should happen with the incoming details and who gets notified. For outbound traffic someone also has to decide which destinations are approved.