Integration
Connect Acadle to redirect.pizza
When New Group fires in Acadle, your agent runs Get Email forward in redirect.pizza. 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 Acadle and redirect.pizza 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 Acadle can start in redirect.pizza
When New Group in Acadle
then Get Email forward in redirect.pizza
When New User in Acadle
then Create Redirect in redirect.pizza
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 Acadle and redirect.pizza
Triggers and actions 3 triggers · 12 actions
Trigger
New GroupTriggers when a new access group is created in your Acadle academy.
Trigger
New UserTriggers when a new user is added to your Acadle academy.
Trigger
User ActivatedTriggers when a user in your Acadle academy becomes active.
Action
Create UserInvites a new user to your Acadle academy and assigns them to one or more groups.
Action
Check domain DNSForces redirect.pizza to re-check the DNS records for a domain and returns the domain's updated status.
Action
Create RedirectCreates a redirect that sends visitors from one or more source domains to a destination URL.
Action
Delete RedirectDeletes a redirect so its source domains no longer forward traffic.
Action
Get DomainReturns one domain with its DNS requirements, verification state and SSL status.
Action
Get Email forwardReturns one email forward, showing which address mail arrives at and where it is delivered.
Action
Get RedirectReturns one redirect with its sources, destination, domains and forwarding settings.
Action
Get Team quotaReturns the connected team, including its plan quota and how much of it is in use.
Action
List DomainsReturns every domain in the connected team, with each domain's DNS requirements, verification state and SSL status.
Action
List Email forwardsReturns every email forward in the connected team, showing which address mail arrives at and where it is delivered.
Action
List RedirectsReturns every redirect in the connected team, with each redirect's sources, destination, domains and forwarding settings.
Action
Update RedirectUpdates an existing redirect: its sources, destination, redirect type, forwarding and tracking settings, tags or notes.
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 Acadle
Acadle to CDNJSCDNJS is a public content delivery network for open-source JavaScript and CSS libraries.
Acadle to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Acadle to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Acadle to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Acadle to Google SheetsGoogle Sheets
Acadle to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into redirect.pizza
HubSpot to redirect.pizzaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to redirect.pizzaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to redirect.pizzaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to redirect.pizzaGoogle Sheets
Gmail to redirect.pizzaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to redirect.pizzaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Acadle and redirect.pizza, answered
What can start an automation from Acadle?
Any of Acadle's 3 triggers in the catalog, including New Group, New User and User Activated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in redirect.pizza when something happens in Acadle?
Any of redirect.pizza's 11 actions, including Create Redirect, Update Redirect, Check domain DNS and Get Domain. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from redirect.pizza to Acadle?
redirect.pizza has no triggers in the catalog today, so automations start in Acadle. If you need the other direction, ask: your agent reads redirect.pizza's API documentation and adds it.
Do I have to build a connector for Acadle or redirect.pizza?
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 Acadle and redirect.pizza 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.