CRM integration guide
Close + UbiGrowth workflows
Close is a CRM built around inbound and outbound calling and sequencing for high-velocity sales teams. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Close part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a CRM workflow around Close with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Lead, Contact, Opportunity, Activity, Call, SMS, and Sequence. Close models Lead as the company-level container with Contacts inside it, which inverts the Salesforce shape. A mapping written as Lead-equals-person produces one Close Lead per contact and destroys the account view.
Close is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
Grow is the usual destination for this connection, because the value shows up as outreach, reply handling, scheduling, and pipeline execution against the connected records.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
The recurring failure with a Close integration is not connectivity. It is that the CRM ends up holding a record of what someone remembered to log, while the work itself happened in an inbox, a call, a spreadsheet, and a separate AI tool that never saw the account.
When that gap exists, everything built on top of it inherits it. Forecasts describe logged activity rather than real activity, outreach is written without the reply history that would make it relevant, and the team spends its day reconciling systems instead of working accounts.
You're likely here because
- Pipeline data is only as current as the last time someone logged activity
- Outreach is generated without the account history that would ground it
- The same account context is rebuilt in several tools each day
Record model
What a Close integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Close's.
Identity and matching
Close models Lead as the company-level container with Contacts inside it, which inverts the Salesforce shape. A mapping written as Lead-equals-person produces one Close Lead per contact and destroys the account view.
Start here
Read Opportunities with no Call or Email Activity in the last week and stage the next touch, using the call outcome history Close already records.
What this will not do
It will not dial for you. Close owns the calling surface; the integration decides who is worth calling and why, and leaves the conversation to the rep.
The constraint to plan around
Call recordings and SMS carry jurisdictional consent requirements that the API will happily let you ignore. Any workflow that acts on call content needs the consent position settled before it runs.
Build notes
What you actually have to reason about in Close.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| status_label | the lead status, and in Close's model this sits on the company-level Lead rather than on a person |
| date_created / date_updated | the sync cursors, with updated moving on any activity including automated ones |
| custom fields | addressed by generated id like Pipedrive, so mappings do not transfer between organisations |
| opportunity value / value_period | recurring versus one-off is a field, not a convention, and totals are wrong if it is ignored |
| contacts[] | an array on the Lead — the person is nested inside the company record, not alongside it |
Authentication
API key per user, with the same visibility caveat as any per-user credential. Close is small enough that teams often use a personal key and then lose access when that person leaves, which is worth deciding deliberately rather than discovering.
Events and delivery
Webhook subscriptions cover the main objects and deliver with retry. Call and SMS events arrive as activity records, which means anything acting on conversation content is acting on data with consent obligations attached.
Workflow
How the Close workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Read the pipeline as it stands
The workflow starts from live Close accounts, contacts, and opportunities rather than an export, so prioritization reflects today's pipeline.
Step 02
Assemble the account context
Reply history, documents, and prior activity are brought together so the next action is grounded in what actually happened with the account.
Step 03
Decide the next action
ARIA proposes the specific next step for the account, with the supporting context attached, instead of producing a message with no stated reason.
Step 04
Execute through Grow
Outreach, reply handling, and scheduling run against the same record, staged for review while the motion is being proven.
Design decisions
The CRM decisions this connection forces.
Each of these has to be settled before the Close workflow is allowed to write anything.
Step 01
Resolve the account identity
Decide how a person and a company are matched between Close and the rest of the stack before any write happens. Most CRM integration damage is duplicate records created by a weak match rule.
Step 02
Keep execution attached to the opportunity
Outreach, replies, meetings, and stage changes should resolve back to the same opportunity, so the CRM reflects what actually happened rather than a parallel activity log.
Implementation path
How to implement the Close workflow.
- 01
Decide which fields Close owns and which the workflow may write, and write that decision down before enabling anything.
- 02
Define the identity match rule for contacts and companies, including what happens on an ambiguous match.
- 03
Start read-only. Prove that the workflow reads the right records before it is allowed to change any of them.
- 04
Once the next-touch queue works, add outcome capture from calls: a structured disposition written back so the queue improves rather than repeating.
Governance
Controls that matter.
Control 01
CRM write scopes are limited to the specific objects the workflow needs, never blanket admin access.
Control 02
Duplicate creation is treated as a defect, not an acceptable side effect of syncing.
Control 03
Stage changes and closed-won updates stay under human control; automation prepares them rather than deciding them.
Failure modes
How a Close integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
The account view fragments — one company appears as a dozen entries.
Cause
A person-level import created one Lead per contact, because Lead is the company container in Close.
Fix
Import at company level with contacts nested, and merge the existing fragments before continuing.
Symptom 02
Call activity appears in Close but not in reporting.
Cause
Activity types are distinct objects and a report querying only one misses the others.
Fix
Query the activity types the workflow cares about explicitly rather than assuming a unified feed.
Symptom 03
Access is lost when a team member leaves.
Cause
The integration used that person's API key.
Fix
Issue the key from a dedicated integration account with the visibility the workflow needs.
What changes at scale
Rate limits are per organisation, and Close's smaller customer size means integrations here are rarely limit-bound. The practical scaling constraint is usually call and SMS volume with its consent obligations rather than API throughput.
Examples
What a working Close workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Pipeline execution
With Close connected, ARIA works from live account, contact, and opportunity records instead of an export, so prioritization reflects the pipeline as it stands today.
Grounded outbound
Grow drafts outreach against the account history already in Close, so the message references what actually happened with the account rather than a generic template.
Limitations and considerations
What to validate before you depend on this.
- Call recordings and SMS carry jurisdictional consent requirements that the API will happily let you ignore. Any workflow that acts on call content needs the consent position settled before it runs.
- Because Lead is the company container, a naive person-level import creates one Lead per contact. The account view then fragments, and reassembling it afterwards is manual because there is no reliable key to merge on.
- When the team is not phone-first. Close's model and pricing assume calling is the primary motion, and a low-call team is paying for a surface it does not use.
- If Close data is incomplete, the workflow inherits that gap. Connected context is not automatically accurate context.
- Custom objects, custom fields, and heavily-customized permission models change what an integration can safely do; validate them against your own instance rather than the vendor default.
FAQ
Close integration questions.
What records does a Close integration actually work with?
The primary records are Lead, Contact, Opportunity, Activity, Call, SMS, and Sequence. Close models Lead as the company-level container with Contacts inside it, which inverts the Salesforce shape. A mapping written as Lead-equals-person produces one Close Lead per contact and destroys the account view.
What should the first Close workflow be?
Read Opportunities with no Call or Email Activity in the last week and stage the next touch, using the call outcome history Close already records.
What will a Close integration not do?
It will not dial for you. Close owns the calling surface; the integration decides who is worth calling and why, and leaves the conversation to the rep.
What is the main constraint to plan around?
Call recordings and SMS carry jurisdictional consent requirements that the API will happily let you ignore. Any workflow that acts on call content needs the consent position settled before it runs.
What changes about a Close integration at scale?
Rate limits are per organisation, and Close's smaller customer size means integrations here are rarely limit-bound. The practical scaling constraint is usually call and SMS volume with its consent obligations rather than API throughput.
How does authentication work for Close?
API key per user, with the same visibility caveat as any per-user credential. Close is small enough that teams often use a personal key and then lose access when that person leaves, which is worth deciding deliberately rather than discovering.
Does Close support webhooks, and can they be trusted?
Webhook subscriptions cover the main objects and deliver with retry. Call and SMS events arrive as activity records, which means anything acting on conversation content is acting on data with consent obligations attached.
What is the risk of writing to Close?
Because Lead is the company container, a naive person-level import creates one Lead per contact. The account view then fragments, and reassembling it afterwards is manual because there is no reliable key to merge on.
When is connecting Close the wrong call?
When the team is not phone-first. Close's model and pricing assume calling is the primary motion, and a low-call team is paying for a surface it does not use.
What should a Close integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Close to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Will this create duplicate records in Close?
Only if the identity match rule is weak. Define how people and companies are matched, and how ambiguous matches are handled, before enabling any write path.
Does Close stay the system of record?
Yes. The design assumption is that Close remains authoritative for the objects it owns and the workflow builds around it rather than replacing it.
Can pipeline stages be updated automatically?
Stage progression should stay under human control. Automation can prepare and propose the update, but deciding that a deal moved is a judgment call.
How this access is governed
What ARIA is allowed to do in Close, and who decides.
Connecting Close is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.