Pitchbound for Lime CRM

Installation and configuration guide · Version 1.0 · November 2026

1. What the integration does

Pitchbound is a sales tool where reps call, hold meetings and send email from one place, with AI support for summaries and next steps. The Lime CRM integration keeps Lime CRM as the system of record: Pitchbound reads persons and companies from Lime, and writes every call, meeting and email back to Lime as a history object on the person.

• From Lime to Pitchbound: persons with name, email, phone, mobile phone, position and company. Reps search and dial them directly from the Pitchbound dialer.
• From Pitchbound to Lime: calls, meetings and emails as history objects, each linked to the person, the person's company and the coworker who made it. The history note carries the outcome, duration, the rep's notes, the AI summary and next steps.
• Never written to Lime: call recordings, meeting recordings, transcripts or links to any of them. These stay in Pitchbound.

2. Requirements

• Lime CRM in the Lime cloud (an address on *.lime-crm.com). On-premise installations are not supported.
• A Lime administrator who can create an API user and API key in Lime Admin.
• A Pitchbound organisation administrator. One organisation can be connected to one CRM at a time.
• The standard Lime CRM core objects person, company, coworker and history. No custom fields or Lime-side configuration is needed.

3. Step 1 – Create an API key in Lime CRM

Done once by the Lime administrator.

1. Open Lime Admin and add a user of type API. Give it a descriptive name, for example "Pitchbound".
2. Give the API user read and write access to person and history, and read access to company and coworker. Pitchbound creates history objects as this user and links each one to the rep's coworker when the email addresses match (see section 5).
3. Click Create API key. The key is shown once; copy it to a safe place.
4. Note the application address. It is the part of the API documentation link before /api/v1/docs/, for example https://yourcompany.lime-crm.com/yourapp. The link is in the user menu of the Lime client when logged in as an administrator.

4. Step 2 – Connect Pitchbound to Lime

Done once by a Pitchbound organisation administrator.

1. In Pitchbound, open Settings → Integrations.
2. On the Lime CRM card, click Connect to Lime CRM.
3. Paste the Lime address (the application address from step 1) and the API key, then confirm.
4. Pitchbound verifies the key against your Lime application and shows the connected address on the card. The connection applies to every user in the organisation.

The API key is stored encrypted and is never shown again in Pitchbound. To rotate it, disconnect and connect again with the new key.

5. What is synchronised

History types. Type keys differ between Lime installations. Pitchbound reads the active options of history.type from your application and tries the keys listed above for each event in order, with unanswered calls trying salescall after noanswer, and then comment. If none of those is active, it uses the first active type in your installation.

Coworker. Each history object is linked to the Lime coworker whose email matches the Pitchbound user who made the call or held the meeting. If there is no match, the object is saved without a coworker.

Company. When the person is linked to a company in Lime, the history object is linked to that company as well.

Writes happen continuously as events occur, not in batches. Nothing is deleted in Lime by Pitchbound.

Example history note for a call

Outbound call via Pitchbound — logged by Anna Andersson
Outcome: Booked meeting
Duration: 7 min 12 s

Call notes
Interested in the Q1 rollout, wants pricing for 25 seats.

AI Call Summary
Anna called Erik at Nordic Supply to follow up on last week's demo. …

Next steps
- Send pricing for 25 seats by Thursday
- Book technical walkthrough with Erik's IT lead

6. Security and data handling

• Only HTTPS connections to *.lime-crm.com are accepted. Addresses resolving to private networks are rejected.
• The API key is held in Pitchbound's encrypted credential store and used server-side only. It is never exposed to the browser.
• Pitchbound reads only the person, company, coworker and history objects listed above. It does not read deals, documents or other objects.
• A typical rep generates a handful of API requests per call.
• Pitchbound's servers, database and AI processing are located in the EU. Recordings and transcripts are never sent to Lime.

7. Disconnecting

1. In Pitchbound, open Settings → Integrations and click Disconnect from Lime CRM on the Lime CRM card. The stored key is deleted.
2. In Lime Admin, delete the API key or the API user. History objects already written remain in Lime.

8. Troubleshooting