Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Keep supported Campfire and Pipedrive records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
Example workflow
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting eventA change involving Campfire Product or Pipedrive Products needs a defined result in the other system.
Start with Campfire Product and Pipedrive Products. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve units, variants, categories, and applicable price lists before order lines.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Review records and field ownershipMapping essentials
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
| Campfire record | Pipedrive record | Record matching | Field ownership |
|---|---|---|---|
| ProductDocumented record: Incremental: ; historical: ; delete detection:Record matching | ProductsDocumented record: ✍️ On Request | Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. | Assign ownership for catalog content, price, and stock separately. |
| FileDocumented record: Incremental: ; historical: ; delete detection:Record matching | FilesDocumented record: ✍️ On Request | Keep file/object ID, container, and version. A path can change and a filename can repeat. | Separate document content, metadata, and sharing permissions; a metadata sync does not imply file transfer or ACL replication. |
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Why teams connect Campfire and Pipedrive
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Campfire and Pipedrive workflow to test, define what success looks like, and decide who handles failed updates.
Show sellers open Campfire Invoice balances on Pipedrive Organizations before renewal conversations.
Keep Pipedrive Persons and Organizations as the single customer master feeding Campfire billing records.
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| Incremental: ✅; historical: ✅; delete detection: ✅. Confirm field permissions and sync direction. |
| Incremental: ✅; historical: ✅; delete detection: ✅ Every 24h. Confirm field permissions and sync direction. |
| Incremental: ✅; historical: ✅; delete detection: N/A (cannot be deleted). Confirm field permissions and sync direction. |
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| ✅ Supported. Confirm field permissions and sync direction. |
| ✍️ On Request. Confirm field permissions and sync direction. |
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | Campfire | Pipedrive |
|---|---|---|
| Integration interface | HTTP endpoints for bot integrations on a self-hosted instance | REST API |
| Authentication | API key | Guided authorization in the Stacksync connection flow; the saved guide does not name the authentication protocol. |
| Change detection | Historical backfill and incremental change tracking are documented. | The saved Stacksync guide does not specify the change-detection mechanism. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Review setup, record relationships, testing, and recovery for your implementation.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Setup guides: Authorize Campfire Connection
Setup guides: Authorize Pipedrive
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Campfire and Pipedrive planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Record matching
Compare whether Campfire Product and Pipedrive Products describe the same product or catalog item in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: Campfire: Product documentationPipedrive: Products documentation
Record matching
Compare whether Campfire File and Pipedrive Files describe the same file or document metadata in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: Campfire: File documentationPipedrive: Files documentation
Use Campfire Product and Pipedrive Products for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Product or Products record needs a defined result in the other system.
Expected result: Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
If it fails: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected File or Files record needs a defined result in the other system.
Expected result: Test a renamed file, a new version, a moved folder, and an access-restricted document.
If it fails: Check the current file version and destination access before retrying transfer or metadata updates.
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A finance-owned record in Campfire needs operational visibility through Deals or Persons.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
The expected product or catalog item relationship is preserved with no duplicate action or unintended write.
Test a renamed file, a new version, a moved folder, and an access-restricted document.
The expected file or document metadata relationship is preserved with no duplicate action or unintended write.
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Only an approved, supported direction and permitted fields are written.
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Inspect Campfire Product and Pipedrive Products, their IDs, and the destination error.
Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Inspect Campfire File and Pipedrive Files, their IDs, and the destination error.
Check the current file version and destination access before retrying transfer or metadata updates.
Check the Campfire and Pipedrive connector guides, account permissions, and any operations marked On Request.
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Detect changesHistorical backfill and incremental change tracking are documented. Delete detection varies by object.
Apply updatesSelected writable fields update in Pipedrive. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesSelected writable fields update in Campfire. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Stacksync connects Campfire and Pipedrive with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Create an API user with a Super User role in Campfire Settings > API Keys and generate its secret. Create a Pipedrive connection in Stacksync and complete the Allow and Install authorization flow. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Start by reviewing Product in Campfire and Products in Pipedrive. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
Use Campfire Product and Pipedrive Products for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 509 integrations listed for Campfire and Pipedrive.
Popular · 4 of 509
Next step
Walk through your Campfire and Pipedrive records, field mappings, and requirements with an integration engineer.
