Connect your app to Pipedrive

Pipedrive is a sales CRM for deals, contacts, leads, and activities. Connect it to Mythos when your team needs a custom view or workflow around the sales records it already maintains in Pipedrive.

The connection uses the API token of a Pipedrive user. It is available in the project chat while building and in your published app, with the access that user has in Pipedrive.

You can use it to:

Read, search, create, and update deals and contacts.
Work with people, organizations, leads, activities, products, and notes.
Use pipeline and stage information to organize a sales dashboard.
Delete supported records when the connected user’s permissions allow it.

Examples to build

These prompts describe apps Mythos can build around your CRM. They do not start an automation simply by connecting Pipedrive.

App idea	Prompt to try	What it adds
Pipeline overview	Show open Pipedrive deals grouped by stage, with filters for owner, value, and expected close date.	A sales-manager view of the existing pipeline.
Customer handoff	Build a handoff page for won deals with the customer, deal notes, and next scheduled activity.	A focused view for the team taking over after a sale.
Lead review queue	Show new Pipedrive leads and let authorized staff assign an owner and record the next qualification step.	A structured review workflow with changes saved to the CRM.
Overdue activities	List overdue activities by salesperson and let them mark a task complete after follow-up.	A daily queue that keeps Pipedrive activity status current.
Customer lookup	Build an internal search for Pipedrive people and organizations, with links to related deals.	A quick CRM reference for support or account teams.
Deal review alerts	Build a view that refreshes high-value deals and highlights stage changes since the last review.	A change-aware view based on periodic CRM reads and the app’s saved comparison.

Specify whether an app is for staff or customers. A shared CRM credential can access more records than a particular app user should see, so a customer-facing portal needs its own account-to-record access rules.

Connect Pipedrive to Mythos

You need a Pipedrive account with API access and permission to create connections in your Mythos workspace. The current setup uses an API token; you do not authorize a Mythos Marketplace app through an OAuth sign-in.

Pipedrive’s API access, quotas, and subscription limits still apply. A connection uses the data and permissions of the token’s owner, so choose the intended user before copying the token.

1. Find your API token

Sign in to the Pipedrive account you want the app to use.
Open your account menu and go to Company settings → Personal preferences.
Select the API tab.
Copy your API token and store it securely.

If the API tab is unavailable, check your Pipedrive account’s API access and permissions. See Pipedrive’s API token guide.

The token already identifies its Pipedrive company. You do not need to enter a company subdomain in Mythos. Treat the token as a password and paste it into the connection form, not the chat.

2. Save the connection

From the Dashboard, open Connectors and select Pipedrive. If no saved connection is available, the setup form opens.
Enter a Display name, such as Sales pipeline.
Paste the token into API token.
Under Sharing, leave it Private or choose Share with others. You can give selected workspace members access or choose Share with workspace.
Click Connect Pipedrive.

If an appropriate connection is already saved and shared with you, use it instead. To link it to an app, open Chat actions (+) → Project connectors in that project, select the saved Pipedrive connection, and click Use in this project.

Then describe the first useful result, for example:

Build a searchable list of people from Pipedrive. Show their organization and open deals. Keep the first version read-only.

Connections in Mythos explains the difference between sharing connection access with people and linking it to a project.

Work with your CRM data

Be specific about the records and operations involved. Deals, leads, people, organizations, activities, and notes serve different purposes in Pipedrive. Mention the fields you want to display or change, and which pipeline or owner should be included.

For example, a handoff dashboard may read won deals and related contacts while keeping its review checklist in the app. Tell Mythos which information should be written back to Pipedrive and which belongs only in the new dashboard.

For changing data, ask for a preview or confirmation in the app before deleting records or making broad updates. The user interface you build determines how staff interact with these actions.

The connector does not register or manage Pipedrive webhooks. If the app needs current data, ask it to fetch the relevant records when a page opens or on a suitable refresh schedule. A webhook workflow requires separate configuration in Pipedrive; connecting an API token alone does not create one.

Limitations and troubleshooting

The connection cannot create a Pipedrive account, change its plan, or grant the connected user new permissions.
It represents one Pipedrive user rather than a separate Pipedrive login for each app visitor.
A valid token does not guarantee access to every record. If data is missing, compare what the token’s owner can see in Pipedrive.
If requests fail after a credential change, check whether the saved token was revoked or regenerated.
For a rate-limit response, reduce repeated or broad refreshes and check the account’s API usage.

Manage your connection

Open Connectors → Pipedrive, then the saved connection. Use Linked projects → Unlink projects to remove access from selected projects. Disconnect stops Mythos from using this connection; the CRM records remain in Pipedrive.

If you replace the API token, disconnect the old connection and connect Pipedrive again with the new token. Link it to the intended projects, ask Mythos to set up the Pipedrive features again, and publish the update. Features using the disconnected connection stop working until they are set up again.