Integration

Connect Pipedrive and MySQL

When New Activity fires in Pipedrive, your agent runs Add Row in MySQL, or New or Updated Row in MySQL to Create Lead in Pipedrive. 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 Pipedrive and MySQL to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start 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)

Pipedrive holds your deals, people and activities; MySQL holds the billing, product or account tables your team queries. Connecting them lets a new deal or person in Pipedrive write into your database, and lets a row change in MySQL create or update the matching Pipedrive record.

Example flows

What Pipedrive and MySQL can do together

From Pipedrive to MySQL

From MySQL to Pipedrive

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 Pipedrive and MySQL

Triggers and actions 10 triggers ยท 30 actions

Each app on its own

Reviews

What our customers say

More from Pipedrive

More into MySQL

Questions

Pipedrive and MySQL, answered

Can a deal in Pipedrive be matched to an existing row in our database?

Yes. When a new deal is created in Pipedrive, the agent can use Find Row in MySQL on a lookup column such as account email, then either update that row or add a new one depending on what came back.

What if a row change in MySQL refers to a person we already have in Pipedrive?

The agent can run Search Persons in Pipedrive with the name or email from the row and use Update Person when a match comes back. If nothing matches, it can use Create Person instead.

What can start an automation from Pipedrive?

Any of Pipedrive's 6 triggers in the catalog, including New Activity, New Deal, New Organization and New Person. Describe the moment in plain language and your agent picks the right one.

What can your agent do in MySQL when something happens in Pipedrive?

Any of MySQL's 6 actions, including Add Row, Find Row via Custom Query, Update Row and Find Row. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from MySQL to Pipedrive?

Yes. When something happens in MySQL, your agent can act in Pipedrive too. This page covers both directions: MySQL's triggers and Pipedrive's actions are listed here as well.

Do I have to build a connector for Pipedrive or MySQL?

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 Pipedrive and MySQL 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.