Integration
Connect Clerk and Device Magic
When New User fires in Clerk, your agent runs Create Group in Device Magic, or New Submission in Device Magic to Create User in Clerk. 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 Clerk and Device Magic 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 Clerk and Device Magic can do together
From Clerk to Device Magic
When New User in Clerk
then Create Group in Device Magic
From Device Magic to Clerk
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 Clerk and Device Magic
Triggers and actions 2 triggers · 22 actions
- New User
Triggers when a new user is created in Clerk.
- Ban User
Ban a user, preventing them from signing in.
- Create Invitation
Invite a new user to the Clerk instance by email; they receive a sign-up link.
- Create User
Creates a new user in Clerk.
- Delete User
Deletes a user from Clerk.
- Unban User
Remove a ban on a user, restoring their ability to sign in.
- Update User
Updates an existing user in Clerk.
- New Submission
Triggers when a form receives a new submission in its Device Magic Database. The form's Device Magic Database destination must be active.
- Approve Device
Approves a device that is waiting to join your organization. Approving an already-approved device has no effect.
- Create Group
Creates a new group in your organization.
- Delete Form
Deletes a form from your organization.
- Delete Group
Deletes a group from your organization.
- Get Device
Returns one device in your organization by its numeric ID or device identifier.
- Get Form
Returns a form's definition: its title and questions.
- List Devices
Returns the devices joined to your Device Magic organization, with owner, groups and approval status.
- List Dispatches
Returns the dispatched forms still outstanding across all devices in your organization.
- List Forms
Returns the forms in your organization with their namespace, version and group.
- List Groups
Returns the groups in your organization with their form and device IDs, optionally filtered by name.
- List Resources
Returns the resources (uploaded files such as images, spreadsheets and PDFs) in your organization.
- List Submissions
Returns submissions stored in a form's Device Magic Database. The form's Device Magic Database destination must be active.
- Remove Device
Removes a device from your organization.
- Revoke Dispatch
Revokes a dispatched form from a device.
- Update Device
Updates a device's owner, description or groups. Fields left blank are unchanged.
- Update Group
Renames a group in your organization.
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 Clerk
Clerk to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Clerk to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Clerk to AnthropicAnthropic builds Claude, a family of large language models.
Clerk to GoHighLevelAll-in-one sales and marketing platform agencies white-label and resell to their clients — contacts...
Clerk to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
Clerk to ElevenLabsElevenLabs is an AI audio research and deployment company.
More into Device Magic
ActiveCampaign to Device MagicActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to Device MagicOrganize anything with Airtable, a modern database created for everyone.
Asana to Device MagicAsana is a collaborative information manager for workspace.
ClickUp to Device MagicClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to Device MagicBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to Device MagicCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
Clerk and Device Magic, answered
What can start an automation from Clerk?
Any of Clerk's 1 trigger in the catalog, including New User. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Device Magic when something happens in Clerk?
Any of Device Magic's 16 actions, including Create Group, Update Device, Update Group and Approve Device. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Device Magic to Clerk?
Yes. When something happens in Device Magic, your agent can act in Clerk too. This page covers both directions: Device Magic's triggers and Clerk's actions are listed here as well.
Do I have to build a connector for Clerk or Device Magic?
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 Clerk and Device Magic 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.