Integration

Connect EquipDash to Knock

When something happens in EquipDash, your agent does the next thing in Knock. Describe it and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want EquipDash and Knock to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

If you run rentals and tours in EquipDash and send your messages through Knock, joining the two keeps the people and records Knock messages about in step with what happens at the counter. New customers, pickups, returns and cancellations in EquipDash become users and objects in Knock, so your email, SMS and push workflows have current details to work from.

Example flows

What EquipDash can start in Knock

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with EquipDash and Knock

Triggers and actions 18 triggers · 43 actions

Each app on its own

Reviews

What our customers say

More from EquipDash

More into Knock

Questions

EquipDash and Knock, answered

Can Knock events start something in EquipDash?

No. Knock has no triggers listed here, so every scenario starts with an event in EquipDash, such as a new customer, a pickup, a return or a cancellation, and then acts in Knock.

What happens if the customer already exists in Knock?

The Add user action creates a user or updates the existing one with the same id, so only the properties you send change. You can also use Get user first if you want to read what is already on file before writing.

What can start an automation from EquipDash?

Any of EquipDash's 18 triggers in the catalog, including Booking Cancelled, Booking Picked Up, Booking Returned and Customer Updated. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Knock when something happens in EquipDash?

Any of Knock's 8 actions, including Add object, Add user, Delete object and Get user. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Knock to EquipDash?

Knock has no triggers in the catalog today, so automations start in EquipDash. If you need the other direction, ask: your agent reads Knock's API documentation and adds it.

Do I have to build a connector for EquipDash or Knock?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.