Integration
Zapier CRM integration
Zapier is how Lumenbase reaches the tools we do not integrate with directly. Triggers fire when something changes in the CRM, actions create or update records from anywhere else, and neither needs a developer.
What syncs
| Object | Direction | What that means |
|---|---|---|
| Triggers | Out of Lumenbase | Record created or updated, deal stage changed, and similar events start a Zap in another tool. |
| Actions | Into Lumenbase | Create or update contacts, companies, and deals from a form, a spreadsheet, a billing tool, or anything else Zapier connects to. |
| Webhooks | Both | For anything Zapier does not cover, the REST API and webhooks do the same job with a little more work. |
Setup, in three steps
Step 1
Create the connection
Settings, then Integrations, then Zapier. Generate a key and paste it into Zapier when it asks for the Lumenbase account.
Step 2
Pick a trigger or an action
Start from what should happen, not from the tool. "When a deal reaches Won, create the project" is a Zap. "Sync everything" is not.
Step 3
Test it with one record
Zapier runs a test with real data. Check where the record landed in Lumenbase before turning the Zap on.
The full walkthrough, including what to do when something does not connect, is in the Help Center: Zapier setup guide
Use it for the edges, not the core
Zapier is at its best joining two systems at a specific, low-volume moment: a form submission creating a lead, a won deal creating a project, an invoice paid updating a field. Those are cheap, they fail loudly, and anyone can fix them.
Where it goes wrong is as a substitute for a real integration. A Zap that keeps two contact databases in step will drift, because it fires on events rather than reconciling state, and a missed run leaves the two permanently different with nothing to tell you.
Bulk writes and why we are careful about them
A Zap that fires per row across a large import is thousands of writes, and any system on the receiving end is entitled to rate limit it. If you are moving a lot of history, use Portage or the API rather than automation, and keep Zapier for the ongoing trickle.