So you want Dock talking to your CRM. Good call—if you do it right, you’ll cut down on double-entry, keep your team in sync, and maybe even make your sales folks a little less grumpy. But let’s be real: integrations are rarely as simple as the marketing page says. This guide walks you through the whole thing, with honest advice on what’s worth your time and what to skip. Whether you’re technical or just the most “tech-comfortable” person on your team, you’ll find the steps below doable.
Who should use this guide?
- You use a CRM (like Salesforce, HubSpot, or Pipedrive) to track deals or customers.
- You’ve started using Dock for client-facing workspaces, proposals, or onboarding.
- You want the two to share data, so you’re not copying info back and forth.
- You don’t have a full-time developer on standby, but you can follow clear, step-by-step instructions.
If that’s you, let’s get to it.
Step 1: Get clear on what you actually want to integrate
Before you click any “Connect” buttons, make a list. What do you really want Dock and your CRM to share?
Common integration goals: - Automatically create Dock workspaces when a deal is created or hits a certain stage in your CRM. - Sync client contact details between Dock and your CRM. - Push activity (like client downloads or views) from Dock back into the CRM. - Link to Dock workspaces from your CRM records, so your team isn’t digging through emails.
What’s not worth integrating? - Every last field. More syncing means more stuff that can break. - Custom automations you “might use one day.” Start simple; add complexity only if it’s painful not to.
Pro tip: Write down your “must-haves” and “nice-to-haves.” This keeps you focused when you’re knee-deep in settings later.
Step 2: Check your CRM’s integration options
Dock offers integrations with several CRMs, but the experience varies. Here’s the honest scoop:
- Supported out of the box: Salesforce, HubSpot, Pipedrive (as of mid-2024)
- Zapier integration: For less common CRMs (or simple, one-way syncing)
- API: For teams with dev resources and very custom needs
What to check: - Does your Dock plan include CRM integrations? (Some are paywalled.) - Does your CRM require admin access to set up integrations? - Are there limits on API calls or sync frequency?
If you’re using a mainstream CRM, you’re likely fine. If you’re on something niche, brace for Zapier or manual work.
Step 3: Connect Dock to your CRM
For Salesforce, HubSpot, or Pipedrive:
- Log into Dock and head to Settings → Integrations.
- Find your CRM and click “Connect.”
- Authorize access. This usually pops up a window from your CRM asking if Dock can access data. Grant only the permissions needed—don’t just click “Allow all” unless you understand the risks.
- Pick your sync settings. You’ll often choose:
- Which object(s) to sync (Deals? Contacts? Companies?)
- One-way or two-way sync
- Field mapping (what matches what)
Watch out for: - Overzealous syncing. Don’t turn on “sync all” unless you want every old record cluttering Dock. - Permissions issues. If you get weird errors, double-check that your CRM user role has the right access.
For Zapier:
- Create a Zap at zapier.com.
- Choose Dock as the trigger or action app (search for “Dock”).
- Choose your CRM as the other side.
- Map fields for the data you want to pass.
- Test the Zap before turning it on.
Reality check: Zapier is best for simple, one-way automations. If you want full syncing or lots of logic, it gets messy (and expensive) fast.
For custom API work:
Only go this route if you have a developer and a really good reason. Check Dock’s API docs, set up a sandbox, and build/test carefully.
Step 4: Map your fields (but keep it simple)
This is where people get ambitious and regret it. The urge to sync every possible field is strong. Resist.
Best practice: - Map only what you’ll actually use: names, emails, company, deal stage. Leave out “Fax number” and other relics. - If Dock lets you, keep your field names the same as your CRM. Saves headaches. - Set up fallback values for missing data if possible.
Pro tip: Keep a shared doc or screenshot of what’s mapped to what. You’ll need it six months from now.
Step 5: Test with a real (but low-stakes) deal
Before you unleash this on your whole pipeline:
- Create a test deal/client in your CRM.
- See if Dock creates a workspace, syncs contacts, and updates activity as expected.
- Try making changes in both systems—does data update the way you expect?
- Check for duplicates or weird formatting.
What to ignore for now: Edge cases (like multi-currency fields or oddball custom properties). Focus on the basics working first.
Step 6: Roll it out—slowly
Once your test works:
- Announce to your team what is integrated and what’s not. Set expectations low.
- Update your internal process docs. (“When you create a deal in CRM, Dock will...”)
- Make yourself available for the first week—people will have questions.
Pro tip: Start with new deals only. Don’t try to sync your entire CRM history unless you enjoy cleanup duty.
Step 7: Keep an eye on it (and fix what breaks early)
Integrations aren’t “set it and forget it.” Check in weekly for the first month:
- Are deals getting stuck?
- Is data going missing?
- Are there new error messages in Dock or your CRM?
If something’s breaking, don’t pile on more features—fix the basics first.
Honest takes: What works, what doesn’t, and what to skip
Works well: - Standard CRMs, simple syncs (contacts, deals, workspace links) - Triggering workspace creation from a deal stage
Can be flaky: - Two-way syncing of every field - Custom fields with weird data types - Syncing old/historical data
Often not worth it: - Integrating fields no one actually uses - Overcomplicating with custom automations before you need them
Skip it for now if: - You have a tiny team and only a handful of deals—you’re probably better off with manual updates at first.
Wrapping up: Start simple, iterate, and don’t overthink it
CRM integrations can save you hours—or waste days if you overdo it. Start with the basics, get real feedback, and only add complexity when it’s actually needed. If you’re hitting a wall, remember: a working, simple integration beats a broken, “perfect” one every time.
Got it working? Great. Now go check your data, ask your team what’s annoying them, and adjust from there. Don’t let the integration run your process—make it serve you.