Connecting Close
Close is where the audit comes from. Connect it once during setup and Bunk3r keeps reading it on a schedule. Only the team’s owner can connect it.
One click
In setup, choose Connect Close and sign in to Close. Close asks you to approve Bunk3r, then sends you back to setup and the first sync starts.
Or paste an API key
- Settings → API Keys. Open Close in a browser, click your avatar top-right, then Settings. API Keys sits in the left column under Company.
- New API Key. Name it Bunk3r so you can revoke exactly this one later. Close shows the key once, when you create it, so copy it before you close the dialog.
- Back in setup, choose Use a Close API key instead and paste it. The key starts with
api_. Bunk3r checks it once, then starts reading.
What Bunk3r reads
- your users, so each lead, call and deal is credited to the right rep;
- leads and their contacts;
- opportunities, with their status and value;
- meetings, including whether they were held, cancelled or a no-show;
- calls, emails and texts, notes, completed tasks and custom activities;
- lead and opportunity status changes, which is how the history of each deal is rebuilt;
- your custom fields, so you can split results by your own lead types and setters.
Why it is read-only
Close does not offer read-only keys: every Close key, and every Close sign-in, can read and write. So Bunk3r enforces read-only itself. It only ever asks Close for data. It never creates, edits or deletes a lead, a deal or a message, and never sends anything from your account.
You stay in control. Revoke the key in Close at any time, or disconnect Close in Bunk3r under Settings → Data sources, which deletes the stored credential.
Something here wrong or missing? Tell us. These pages are part of the product.