What we do
Tools
Industries
Department
How we workLet's talk →
Home/Close
Close CRM

Close Integrations: What Works Natively, What Runs Through Zapier, What Needs a Build

Close's integration directory lists well over a hundred apps, and they cluster around what Close is for: email, calendars, calling, meeting notes, lead data and marketing. What you won't find there is accounting or billing. No QuickBooks, no Xero, no Stripe, and no Slack either. Here's what connects which way, so you can tell in a minute whether your stack is covered.

Where Close stops

It gets reps on the phone faster, but once they hang up, someone still creates the invoice and tells delivery by hand.

Stuck on Close? Let's solve it →

Does Close integrate with...

Tool Route What to know
Gmail, Microsoft 365, Google Calendar Listed in Close's directory. Email and meetings sync onto the lead. This is the integration most teams set up first.
Calendly, SavvyCal and other scheduling tools Listed. Calendly is among the most used. Booked meetings and new contacts land in Close without a rep logging them.
Zoom, Gong, Fireflies, other calling and call-notes tools Listed. Close also has its own built-in calling and SMS. Check whether you need the outside dialer at all before paying for both.
HubSpot and email marketing tools HubSpot is listed, along with tools like Drip and Customer.io. Decide which system owns the contact. Two-way sync between two CRMs needs a rule for who wins. See HubSpot.
Segment, Fivetran, Airbyte and other data tools Listed. Good for getting Close data into a warehouse for reporting, or product signups into Close.
Slack Not in the directory. Teams use Zapier or Make. Fine for a "deal won" ping. Anything with conditions, such as only deals above a value, gets fiddly fast.
QuickBooks, Xero, Stripe Not in the directory. Zapier or Make templates, or a direct build on the Close API. This is the handoff that matters most and breaks most often. The pitfalls below cover it.
Your own product or billing system The Close API, with API keys for scripts and OAuth for apps, plus webhooks. Endpoint detail is on our Close API page.

Zapier and Make, or a direct build on the Close API

Start here

Zapier or Make

  • A new lead creates a task, a won deal posts a message, a form fill creates a lead.
  • Set up in an afternoon by whoever runs Close.
  • Each run handles one event on its own, with no memory of what it did last time.
When money is involved

A direct build

  • Checks before it acts: is there already an invoice for this deal, is the customer already in QuickBooks.
  • Copes with Close's webhook rules: events can arrive out of order and get retried.
  • Logs every handoff so finance can see which deals were invoiced and which weren't.

If a duplicate or missed run only costs a Slack message, use Zapier or Make. If it costs an invoice, build it properly.

Where Close-to-billing connections break

A deal marked Won twice

How you'll know: A rep moves an opportunity back to Active to fix the value, then to Won again, and the customer gets two invoices.

Fix: Store the Close opportunity ID on the invoice and check for it before creating another. Changes to a won deal should update the invoice, not add one.

Events that arrive out of order

How you'll know: The invoice shows the old deal value, even though the rep corrected it straight after winning it.

Fix: Close doesn't guarantee webhook order. Read the opportunity fresh from the API when the event arrives, instead of trusting the values in the payload.

A webhook subscription that quietly paused

How you'll know: Nothing has reached accounting for days, and no error showed up anywhere you look.

Fix: Close pauses a subscription after three days of failed deliveries, or when its backlog hits 100,000 events, and emails the admins. It has to be switched back on through the API. Watch for those emails, and replay missed events from Close's event log, which keeps 30 days.

One heavy integration slowing all the others

How you'll know: A bulk import runs and the dialer integration and your Zaps start failing with rate limit errors.

Fix: Close's rate limits are shared across the whole organization, with a lower cap per API key. Give each integration its own key and have it wait for the reset Close returns.

An inside-sales software team: from a Slack message to a real handoff

A software company whose reps close deals by phone all day in Close.

Before

When a rep won a deal, the handoff was a Slack message and a row in a spreadsheet.

Account setup started whenever someone in customer success happened to notice.

After

Marking the deal won in Close now starts account setup, billing and a welcome sequence at the same time.

Customer success gets a task with the call notes already attached.

Questions people ask

What is Close (the CRM)?

A CRM built for inside sales teams, with calling, SMS and email sequences built in next to the pipeline, so reps can work a list without switching apps. It's a sales tool, not a general business system.

Is Close the same as Close.io?

Yes. Close.io was the original name. The company dropped the ".io" and now goes by Close, at close.com.

How much does Close cost?

Close charges per user per month, across tiers that differ mainly in calling, automation and reporting. There's a free trial rather than a free plan. Prices change, so check Close's pricing page.

Does Close have an API?

Yes, a REST API covering leads, contacts, opportunities and activities, plus webhooks for events. Scripts use an API key, and apps other people install use OAuth. It's the route for anything Close's directory doesn't cover, including accounting.

Where do I log into Close?

At app.close.com, with your Close account.

Does Close integrate with other tools?

Yes. Its directory lists well over a hundred, mostly email, calendar, calling, lead data and marketing tools, plus Zapier and Make for the rest. Accounting and billing tools are the gap.

Does Close integrate with QuickBooks or Stripe?

Not natively. Neither is in Close's integration directory. Zapier and Make have templates that create a QuickBooks customer or invoice from a Close event, and a direct API build handles duplicates, corrections and payment status coming back. Our QuickBooks HubSpot integration page shows how the same problem looks from another CRM.

Who builds a Close integration when Zapier isn't enough?

Once Zapier runs out, n-frames takes it from there. We build directly on the Close API and webhooks, handle the retries and pauses, and keep running the integration so a missed invoice turns into an alert, not a month-end surprise. For other sales tools, see Pipedrive integrations or Copper.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.