Pipedrive Integration

Connect Cothon with Pipedrive to track government opportunities as deals in your existing pipeline. Cothon pushes opportunities, bid analysis results, and proposal status to Pipedrive, and deal changes made in Pipedrive can flow back through webhooks.

Connecting

1. Go to Settings → Integrations → Pipedrive and click Connect.
2. Sign in to Pipedrive and authorize Cothon.
3. You are returned to Cothon with the connection active.

The connection uses OAuth 2.0. Tokens are stored securely and refreshed automatically; your Pipedrive password is never seen or stored by Cothon.

Automatic custom fields

When you connect, Cothon can provision a set of custom deal fields in your Pipedrive account so analysis results are visible directly on the deal. Existing fields with the same labels are reused, never duplicated:

You can re-run provisioning at any time from the Pipedrive settings page, and view the current field mapping there.

What syncs

Opportunities → deals

Each synced opportunity becomes a Pipedrive deal with its title, value, and expected close date, plus the custom fields above. The first sync creates the deal and stores its ID on the Cothon opportunity; later syncs update the same deal rather than creating duplicates.

Analyses and proposals

Completed bid analyses update the linked deal's analysis fields (status, requirement counts, confidence) and attach a summary note. Generated proposals update the proposal status and quality fields.

Pipedrive → Cothon (webhooks)

Cothon receives Pipedrive webhook events (deals, people, organizations, activities, and notes, in both v1 and v2 webhook formats). When a synced deal changes in Pipedrive — title, value, or expected close date — the matching Cothon opportunity is updated. Webhook payloads are signature-verified before processing.

Pipelines and stage mapping

Pipedrive stages are yours to define, so Cothon lets you map them explicitly:

1. On the Pipedrive settings page, Cothon lists your pipelines and stages, fetched live from your account.
2. Map each Cothon opportunity stage to a Pipedrive stage.
3. Optionally set a default pipeline and default stage for newly created deals without a mapping.

When an opportunity syncs, its deal is placed in the mapped stage; if no mapping exists, the default stage is used.

Sync settings

In Settings → Integrations → Pipedrive you can configure:

• Auto-sync toggles — separately enable automatic sync for opportunities, analyses, and proposals
• Sync on status change — push an update whenever an opportunity's status changes
• Create activities — log activities on the deal as work progresses
• Sync frequency — how often automatic sync runs
• Default pipeline / stage — where new deals land
• Sync filters — limit sync by stage and by minimum opportunity value

Manual sync and the sync log

• Sync a single opportunity, analysis, or proposal on demand from its page.
• Use Sync all on the settings page to push everything pending.
• The sync log records each sync attempt with its direction, timestamp, and result — the first place to look when a deal seems out of date.

Disconnecting

Click Disconnect on the Pipedrive settings page. Stored tokens are deleted and syncing stops immediately. Deals and custom fields already in Pipedrive remain there; nothing is deleted on either side. You can reconnect later without losing the field mapping.

Troubleshooting

Next steps

• Salesforce — alternative CRM option
• Slack — add team notifications
• Opportunities — managing opportunities in Cothon