Most 'CRM automation' is a form that emails the office and a human who pastes it into HubSpot. The CRM then reports whatever the last person typed. Ads, the website, the phone, and the invoice system each tell a different story about the same customer.
KeenCraft's automation and CRM integration work exists to make one record the system of truth. The brand of CRM matters less than whether source, stage, and cash survive from first touch to paid job.
What a production write-path looks like
A webhook that creates a contact is not an integration. A working write-path does four things in order:
- Identify: match email, phone, or CRM id so you do not mint a duplicate every form submit.
- Create or update: map fields the staff already use, including source, campaign, and landing page.
- Advance: move stage when the real-world event happens (booked, quoted, invoiced), not when a zap feels like it.
- Write back: send the money event to ads or analytics so bid strategy sees jobs, not thank-you pages.
The trades CRM KeenCraft built for local services is the full version of that loop: leads auto-scored 1–100, form submissions mapped into records, email by job stage, jobs tracked to invoice, and revenue attributed to source including Google Ads through officially verified OAuth.
HubSpot, Salesforce, Zoho, or a custom CRM
Stay on the CRM you already run
If sales already lives in HubSpot, Salesforce, or Zoho, the job is usually OAuth, object mapping, and workflow triggers, not a rewrite. Custom objects, associations, and permission models are where generic zaps go quiet. That glue is still automation work, not a new product.
Build when the workflow is the product
Trades businesses that need lead scoring, a job board, quotes, invoices, and ads attribution in one tenanted system often cannot get there by stacking three SaaS tools. That is when custom software is cheaper over two years than the integration tax.
On PARKees, the related problem was tying marketing spend to real bookings with last non-direct-click attribution. The CRM row still had to carry UTMs and referrers. Ads pixels alone never reconcile with invoices. See attribution tracking for bookings for the measurement model.
Gmail, voice, and chat belong on the same thread
Operators do not experience 'channels.' They experience one customer who emailed, then called, then filled a form. Dynaris is a live AI front desk that unifies voice, chat, and email, with MCP-isolated agent tools and Gmail automation via Composio. Isolation per workspace is a correctness requirement: one client's tools cannot see another client's mailbox. The buying version of that architecture is an AI front desk that is more than a phone agent.
The same rule applies when a voice agent books after hours. Copy source, campaign, and call outcome onto the CRM record. Do not let a receptionist overwrite it with 'phone.' Phone is a channel. It is not a campaign.
OAuth, webhooks, and the failure modes that wake you up
- Token refresh: unattended integrations die on Monday because a sandbox token expired Friday.
- Idempotency: retries from the form vendor must not create three contacts.
- Partial updates: a failed stage move should not leave a paid invoice on 'new lead.'
- Rate limits: bulk imports and live form storms are different designs.
- Human edits: last-write-wins will erase the ads click id a closer typed over. Protect source fields.
This is data and backend architecture sold as part of an operations outcome, not as an open research bucket. PostgreSQL, Redis, and queueing show up because HubSpot's API will not be your source of truth for a high-volume pipeline you also have to report on.
A sequence you can actually start
- List the money events: form, call, chat, quote sent, invoice paid.
- Pick the system of record for each object. One, not three.
- Map fields including source. If source is optional, it will be empty.
- Use official OAuth for CRM and ads. No unofficial scrapers.
- Turn off the duplicate path (the 'also email the office' zap) once the write-path is trusted.
- Review weekly: spend vs booked jobs vs paid invoices.
KeenCraft delivers this as a fixed-price Statement of Work. If two of your tools already contain the same customer and neither is trusted, that is the engagement, not another dashboard.