Integration
Connect Pipedrive to Instatus
When New Activity fires in Pipedrive, your agent runs Add component in Instatus. 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 Instatus to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Pipedrive can start in Instatus
When New Activity in Pipedrive
then Add component in Instatus
When New Deal in Pipedrive
then Add incident update in Instatus
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 Instatus
Triggers and actions 5 triggers · 38 actions
Trigger
New ActivityTriggers when a new activity is created.
Trigger
New DealTriggers when a new deal is created.
Trigger
New OrganizationTriggers when a new organization is added.
Trigger
New PersonTriggers when a new person (contact) is added.
Trigger
New Person (with Custom Fields and Labels)Triggered when a new person (contact) is added. Includes custom fields and labels.
Action
Create ActivityCreates a new activity (call, meeting, task, etc.).
Action
Create DealAdds a new deal to Pipedrive. Returns the created deal.
Action
Create LeadCreates a new lead. Returns the created lead.
Action
Create NoteAdds a new note to a deal, person, or organization.
Action
Create OrganizationAdds a new organization. Returns the created organization.
Action
Create PersonAdds a new person (contact). Returns the created person.
Action
Delete ActivityMarks an activity as deleted.
Action
Delete DealMarks a deal as deleted.
Action
Delete OrganizationMarks an organization as deleted.
Action
Delete PersonMarks a person as deleted.
Action
Get DealReturns the deal with the given ID.
Action
Get OrganizationReturns the organization with the given ID.
Action
Get PersonReturns the person with the given ID.
Action
Get related deals for personReturns deals having the specified status that are related to the specified person.
Action
Get stage ID by stage nameReturns the stage id if the stage name exists.
Action
Merge organizationsMerges two organization accounts. Info from the organization record to discard is merged into the organization record to keep.
Action
Merge personsMerges two person accounts. Info from the person record to discard is merged into the person record to keep.
Action
Search DealsSearches deals by term. Returns matching deals.
Action
Search OrganizationsSearches organizations by term. Returns matching organizations.
Action
Search PersonsSearches persons by term (name, email, phone). Returns matching persons.
Action
Update ActivityUpdates an existing activity by ID.
Action
Update DealUpdates an existing deal by ID.
Action
Update OrganizationUpdates an existing organization by ID.
Action
Update PersonUpdates an existing person by ID.
Action
Add componentCreates a new component on an Instatus status page and returns the created component.
Action
Add incident updatePosts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses.
Action
Add maintenanceSchedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options.
Action
Add subscriberAdds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones.
Action
Create IncidentCreates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers.
Action
Delete incidentDeletes an incident from an Instatus status page.
Action
Get componentReturns one component on an Instatus status page, including its name, current status, description and group.
Action
Get incidentReturns a single incident on a status page, including its updates, affected components and the teammate who created it.
Action
Get maintenanceReturns one scheduled maintenance on a status page, including its updates and affected components.
Action
List componentsReturns the components on an Instatus status page, with each component's name, status and group.
Action
List maintenancesReturns the scheduled, in-progress and completed maintenances on an Instatus status page.
Action
List status pagesReturns the status pages in your Instatus account, including each page's id, name, subdomain and current status.
Action
List subscribersReturns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status.
Action
Update componentUpdates a component on an Instatus status page, such as its name, description, status, order or group.
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 Pipedrive
Pipedrive to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pipedrive to Google SheetsGoogle Sheets
Pipedrive to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Pipedrive to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Pipedrive to MailchimpMailchimp marketing automation and email platform.
Pipedrive to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Instatus
HubSpot to InstatusHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to InstatusSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to InstatusSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to InstatusGoogle Sheets
Gmail to InstatusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to InstatusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pipedrive and Instatus, answered
What can start an automation from Pipedrive?
Any of Pipedrive's 5 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 Instatus when something happens in Pipedrive?
Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Instatus to Pipedrive?
Instatus has no triggers in the catalog today, so automations start in Pipedrive. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it.
Do I have to build a connector for Pipedrive or Instatus?
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.
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.