Integration

Connect Adafruit IO and Doclift PDF

When something happens in Adafruit IO or Doclift PDF, your agent does the next thing in the other. 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 Adafruit IO and Doclift PDF 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)

Doclift PDF generates documents through its API, and Adafruit IO stores readings and messages on feeds. Joining them lets a finished document request push its tag or signed file link onto a feed, and lets a new feed reading drive template work in Doclift PDF, such as publishing a template or updating a variable's allowed values.

Example flows

What Adafruit IO and Doclift PDF can do together

From Adafruit IO to Doclift PDF

From Doclift PDF to Adafruit IO

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 Adafruit IO and Doclift PDF

Triggers and actions 2 triggers · 12 actions

Each app on its own

Reviews

What our customers say

More from Adafruit IO

More into Doclift PDF

Questions

Adafruit IO and Doclift PDF, answered

How does the agent know a Doclift PDF document is ready?

Doclift PDF sends its completion callback to the New PDF Document Generated webhook trigger, which starts the run. From there the agent can read the document request for status and the signed file url, then write what you need to an Adafruit IO feed.

Can a feed reading change a template in Doclift PDF?

Yes. A New Feed Data Point in Adafruit IO can trigger Doclift PDF actions such as List Templates, Add Variable, Update Variable or Publish Template, so a reading can add a variable or publish a template. The agent tests every scenario before it runs on live data.

What can start an automation from Adafruit IO?

Any of Adafruit IO's 1 trigger in the catalog, including New Feed Data Point. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Doclift PDF when something happens in Adafruit IO?

Any of Doclift PDF's 11 actions, including Add Variable, List Templates, Publish Template and Update Variable. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Doclift PDF to Adafruit IO?

Yes. When something happens in Doclift PDF, your agent can act in Adafruit IO too. This page covers both directions: Doclift PDF's triggers and Adafruit IO's actions are listed here as well.

Do I have to build a connector for Adafruit IO or Doclift PDF?

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.