Integration
Connect thanks.io and Clerk
When New Order fires in thanks.io, your agent runs Create User in Clerk, or New User in Clerk to Lookup Address by Email in thanks.io. 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 thanks.io and Clerk to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart 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)Example flows
What thanks.io and Clerk can do together
From thanks.io to Clerk
When New Order in thanks.io
then Create User in Clerk
When Item Delivered in thanks.io
then Update User in Clerk
From Clerk to thanks.io
When New User in Clerk
then Lookup Address by Email in thanks.io
When New User in Clerk
then Add Recipient in thanks.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 thanks.io and Clerk
Triggers and actions 4 triggers · 9 actions
Trigger
Item DeliveredTriggers when a postcard, letter, notecard, or giftcard is delivered to a recipient.
Trigger
New OrderFires once for each new order placed in your thanks.io account.
Trigger
QR Code ScanTriggers when a QR Code on a postcard, letter, or notecard is scanned. This will also trigger when a giftcard is redeemed.
Action
Add RecipientAdds a recipient to your account and to an optional list. Only US or Canadian addresses are accepted. If no/invalid address is specified and a valid email address is, we'll attempt to look up a valid street address using the email address for a fee.
Action
Delete RecipientDeletes a Recipient from Mailing List.
Action
Lookup Address by EmailReturns the mailing address on file for a recipient in a thanks.io mailing list, looked up by their email address. Returns an empty list of matches when no recipient in that list has the email.
Trigger
New UserTriggers when a new user is created in Clerk.
Action
Ban UserBan a user, preventing them from signing in.
Action
Create InvitationInvite a new user to the Clerk instance by email; they receive a sign-up link.
Action
Create UserCreates a new user in Clerk.
Action
Delete UserDeletes a user from Clerk.
Action
Unban UserRemove a ban on a user, restoring their ability to sign in.
Action
Update UserUpdates an existing user in Clerk.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from thanks.io
thanks.io to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
thanks.io to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
thanks.io to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
thanks.io to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
thanks.io to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
thanks.io to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into Clerk
Brevo to ClerkBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Instagram to ClerkInstagram is a social media platform for sharing photos, videos, and stories.
Kit to ClerkKit is an email marketing platform for professional bloggers.
Postman to ClerkPostman is a platform for building and testing APIs.
Telegram to ClerkTelegram is a cloud-based instant messaging and voice over IP service developed by Telegram Messenger LLP.
HubSpot to ClerkHubSpot is your all-in-one stop for all of your marketing software needs.
Questions
thanks.io and Clerk, answered
What can start an automation from thanks.io?
Any of thanks.io's 3 triggers in the catalog, including New Order, Item Delivered and QR Code Scan. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Clerk when something happens in thanks.io?
Any of Clerk's 6 actions, including Create Invitation, Create User, Update User and Ban User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Clerk to thanks.io?
Yes. When something happens in Clerk, your agent can act in thanks.io too. This page covers both directions: Clerk's triggers and thanks.io's actions are listed here as well.
Do I have to build a connector for thanks.io or Clerk?
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 thanks.io and Clerk 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.