Pro plan. Close works through a connection, HTTP steps and listeners (Wait for webhook, Call & wait), which are part of Pro and Agency (and the free trial). Anything you already have keeps working on every plan. See Plans and billing.
How it connects: Close’s API with an API key (basic auth). See Close’s create a lead and create a contact docs. Requests and answers follow Close’s docs.
Before you start
- An API key: in Close, open Settings > Developer > API Keys and create one.
1. Connect Close
In Kerux, open Integrations > Connections, click Connect on Custom API (under Developers):- How it signs in: Username and password: the API key as user name, the password empty.
- Base URL:
https://api.close.com
2. Create the Close lead when someone replies
A contact who replies leaves the campaign (the When the contact replies box). In that box, add Send to another campaign and pick a short “Replied: to Close” campaign. Its first step is a Webhook / HTTP step with the Close connection:id and url: {{steps.<step>.response.body.id}}.
3. React to status changes in Close
Close webhooks are created with a call to Close’s webhook endpoint (see Close’s webhook docs), for example for Close lead updates. Point it to a Kerux Wait for webhook step with One shared URL + a match rule, matched on the Close lead id from step 2. Click Listen for test event, change a test lead’s status in Close, and branch on the status field from the sample.Test with one contact
In the follow-up campaign’s Builder, click Test to open Test on one contact, then open the lead in Close from theurl in the answer.
Common errors
400 about urls or emails
400 about urls or emails
Each email needs its
type. Keep office as above or use a type Close lists.Two Close leads for the same company
Two Close leads for the same company
Creating a lead doesn’t merge with an existing one. Search Close first and add the contact to the existing lead with the contacts endpoint and its
lead_id.