Integration

Connect Perigon to TemplateDocs

When New article fires in Perigon, your agent runs Add template in TemplateDocs. Describe the whole flow 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 Perigon and TemplateDocs 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

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. 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)

Perigon watches the news for the queries you care about, and TemplateDocs holds the Word templates your team writes from. Joining them means a new article in Perigon can reach into TemplateDocs on its own: checking which templates exist, reading the placeholder tags inside one, renaming it, or clearing out a template you no longer use.

Example flows

What Perigon can start in TemplateDocs

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 Perigon and TemplateDocs

Triggers and actions 1 trigger · 14 actions

Each app on its own

Reviews

What our customers say

More from Perigon

More into TemplateDocs

Questions

Perigon and TemplateDocs, answered

Can an article from Perigon fill in a document for me?

The TemplateDocs actions here cover templates themselves: listing them, reading one with its placeholder tags, adding, renaming and deleting. So a new article in Perigon can fetch the tags a template expects, which tells your team exactly which fields a brief needs.

Does this only work one way, from Perigon into TemplateDocs?

TemplateDocs has no triggers listed, so every scenario starts with a new article in Perigon. From there the agent can also call back into Perigon for stories, people or journalists before it touches TemplateDocs, and it tests each scenario before it runs.

What can start an automation from Perigon?

Any of Perigon's 1 trigger in the catalog, including New article. Describe the moment in plain language and your agent picks the right one.

What can your agent do in TemplateDocs when something happens in Perigon?

Any of TemplateDocs's 5 actions, including Add template, Delete template, Get template and List templates. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from TemplateDocs to Perigon?

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

Do I have to build a connector for Perigon or TemplateDocs?

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.

Can my AI client use Perigon and TemplateDocs without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

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.