Integration
Connect Cartes and Targetprocess
When New marker fires in Cartes, your agent runs Create Task in Targetprocess, or New Bug in Targetprocess to Add map in Cartes. 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 Targetprocess 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 and Targetprocess can do together
From Cartes to Targetprocess
When New marker in Cartes
then Create Task in Targetprocess
From Targetprocess to Cartes
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 Targetprocess
Triggers and actions 12 triggers · 19 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.
- New Bug
Triggers when a new Bug is added in Targetprocess.
- New Build
Triggers when a new Build is added in Targetprocess.
- New Comment
Triggers when a new Comment is added in Targetprocess.
- New Feature
Triggers when a new Feature is added in Targetprocess.
- New Iteration
Triggers when a new Iteration is added in Targetprocess.
- New Release
Triggers when a new Release is added in Targetprocess.
- New Request
Triggers when a new Request is added in Targetprocess.
- New Task
Triggers when a new Task is added in Targetprocess.
- New Team Iteration
Triggers when a new Team Iteration is added in Targetprocess.
- New Time
Triggers when a new Time record is added in Targetprocess.
- New User Story
Triggers when a new User Story is added in Targetprocess.
- Add Requester to Request
Creates a Requester and attaches them to an existing Request.
- Change State
Changes the workflow state of an existing entity.
- Create Bug
Creates a new Bug in a Targetprocess project.
- Create Build
Creates a Build in a Targetprocess project.
- Create Feature
Creates a Feature, a high-level requirement that groups User Stories.
- Create Request
Creates a Request (an idea, issue or question from users).
- Create Task
Creates a Task under an existing User Story.
- Create User Story
Creates a User Story in a project.
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
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 Targetprocess
Questions
Cartes and Targetprocess, 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 Targetprocess when something happens in Cartes?
Any of Targetprocess's 8 actions, including Create Bug, Create Build, Create Feature and Create Request. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Targetprocess to Cartes?
Yes. When something happens in Targetprocess, your agent can act in Cartes too. This page covers both directions: Targetprocess's triggers and Cartes's actions are listed here as well.
Do I have to build a connector for Cartes or Targetprocess?
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 Targetprocess 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.