Connecting your tools

Connecting Zapier to an AI agent

Zapier is not one more tool on the list: it is a relay towards thousands of others. Where each connector in the catalogue opens one service, this one opens access to everything your Zapier account knows how to reach — including the niche software of your trade, the one that will never have a dedicated connector anywhere. It is powerful, and it deserves to be understood before being connected, because this relay moves the place where the scope is set.

1. What Zapier brings that no other connector brings

The nullbot catalogue covers the services most businesses use: email, calendar, sales, payment, storefront, social networks, files. It does not cover — and never will — the scheduling software of a driving school, the fleet-tracking tool of a haulier or the booking platform of one particular sector.

That is exactly where Zapier serves. If your business software has a Zapier integration, an agent can reach it through this relay, without waiting for a dedicated connector to exist.

The two situations where it is clearly the right choice:

The niche software. The one nobody outside your trade has ever heard of, and on which the essential of your organisation nevertheless depends.
The chain already built. If your business already has Zapier automations in place, the agent plugs into them rather than redoing the work alongside.

2. A token to paste, not an account sign-in

Zapier connects differently from most connectors: there is no "sign in with my account" button. You create a connection in your Zapier account, it gives you a token, and you paste it once into nullbot.

This token is treated as a secret: it is stored encrypted and never displayed again. Two consequences follow, which set Zapier apart from account-connection connectors:

Revocation happens at Zapier. To cut off access, you delete the connection in Zapier — that is where the authority lives, and that is where it is withdrawn.
The scope is defined at Zapier. What the agent can reach is exactly what that Zapier connection exposes. This is the most important point on this page.

So our recommendation is clear: create a Zapier connection reserved for nullbot, and expose to it only the actions your agents genuinely need. Reusing an existing connection already open to everything is the shortcut that makes the scope uncontrollable — and this time, the limit is not on our side.

3. What one more layer costs

A relay is a convenience, never a gift. Three costs, to be weighed:

One more dependency. The chain becomes agent → Zapier → your tool. If Zapier has an incident or if your subscription changes, access stops without either your tool or nullbot having moved.
One more subscription. Zapier is a paid service, with its own execution quotas. An active agent consumes those quotas, and it is better to plan for it than to discover it on an invoice.
Slightly less precision. A direct connector names its resources — this mailbox, this sheet, this channel — and validation before writing applies to an identified action. Through a relay, the granularity is the one Zapier exposes, which is sometimes coarser.

Hence a simple rule: when a direct connector exists for a service, take it. Gmail, Slack, Notion, Stripe, Shopify and the others connect better directly — better scope, one-click revocation, no intermediate dependency. Zapier is made for what has no door of its own.

It remains classified at the high stakes level, with human validation before writing active by default. And each agent's spending is reserved before the model call, exactly as everywhere else — the mechanism is described separately.

4. What it changes over time

The value of a relay is measured less at the first connection than in the unforeseen needs of the following months.

Week 1. The business tool that seemed out of reach becomes reachable. It is often the one that was blocking the whole rest of the project.
Month 3. New needs no longer require waiting: if the application is at Zapier, it is reachable the day you need it.
Year 2. The uses that have grown in importance deserve to be re-examined. If a direct connector has appeared in the meantime for a service you were routing through Zapier, switching to it removes a layer, a dependency and a cost.

No figured gain is promised: it depends on the tools you use and on what your Zapier account exposes.

5. Frequently asked questions

Is a paid Zapier subscription required?

Connecting requires a Zapier account able to create a connection and expose actions, which falls under Zapier's paid plans. Execution quotas are those of your Zapier subscription, independently of nullbot.

Can you limit what the agent reaches through Zapier?

Yes, and it is at Zapier that this is set: the connection you create defines the exposed actions. That is the major difference with direct connectors, where the scope is named within nullbot. The right instinct is a dedicated Zapier connection, deliberately narrow.

Zapier or a direct connector: which is better?

A direct connector, whenever one exists: finer scope, immediate revocation, one less dependency and no third-party quota. Zapier is the right choice for tools that have no connector — and they are numerous as soon as you step outside mainstream software.

What happens if I delete the connection at Zapier?

Access stops immediately: the token is worth nothing any more. It is the most direct way to cut an agent off from everything that passed through that relay, and it depends on you alone.