Integration
Connect Cartes to redirect.pizza
When New marker fires in Cartes, 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 Cartes 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 Cartes can start in redirect.pizza
When New marker in Cartes
then Get Email forward 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 Cartes and redirect.pizza
Triggers and actions 1 trigger · 22 actions
- New marker
Triggers when a new marker is added to a Cartes map.
- Add map
Creates a new map on Cartes.io and returns it, including the one-time map token needed to edit or delete it.
- Add marker
Adds a marker at a latitude and longitude on a Cartes.io map, in an existing or new category.
- Delete map
Deletes a map from Cartes.io.
- Delete marker
Deletes a marker from a Cartes.io map.
- Find maps by keyword
Returns public Cartes.io maps that match a keyword.
- Get map
Returns a single Cartes.io map, including its title, description, privacy setting and categories.
- List categories
Returns all marker categories available on Cartes.io.
- List maps
Returns the public maps on Cartes.io, optionally filtered by ID, category or query.
- List markers
Returns all markers on a Cartes.io map, optionally including expired ones.
- Update map
Updates the title, description, privacy or marker-creation setting of an existing Cartes.io map.
- Update marker
Updates a marker on a Cartes.io map: change its description, or (as the map owner) flag it as spam.
- Check domain DNS
Forces redirect.pizza to re-check the DNS records for a domain and returns the domain's updated status.
- Create Redirect
Creates a redirect that sends visitors from one or more source domains to a destination URL.
- Delete Redirect
Deletes a redirect so its source domains no longer forward traffic.
- Get Domain
Returns one domain with its DNS requirements, verification state and SSL status.
- Get Email forward
Returns one email forward, showing which address mail arrives at and where it is delivered.
- Get Redirect
Returns one redirect with its sources, destination, domains and forwarding settings.
- Get Team quota
Returns the connected team, including its plan quota and how much of it is in use.
- List Domains
Returns every domain in the connected team, with each domain's DNS requirements, verification state and SSL status.
- List Email forwards
Returns every email forward in the connected team, showing which address mail arrives at and where it is delivered.
- List Redirects
Returns every redirect in the connected team, with each redirect's sources, destination, domains and forwarding settings.
- Update Redirect
Updates 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 Cartes
Cartes to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cartes to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cartes to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cartes to Google SheetsGoogle Sheets
Cartes to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cartes to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into redirect.pizza
Questions
Cartes and redirect.pizza, answered
What can start an automation from Cartes?
Any of Cartes's 1 trigger in the catalog, including New marker. 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 Cartes?
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 Cartes?
redirect.pizza has no triggers in the catalog today, so automations start in Cartes. 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 Cartes 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 Cartes 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.