> For the complete documentation index, see [llms.txt](https://help.botpenguin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.botpenguin.com/bots/website-mobile-app-bot/3rd-party-integrations/botpenguin-integrations/integrate-botpenguin-with-pipeline.md).

# Integrate BotPenguin with Pipeline

### What is Pipeline CRM Integration?

Pipeline CRM Integration allows you to connect BotPenguin with Pipeline CRM and automatically send chatbot-generated leads into your CRM. When a user completes a chatbot conversation, their details are transferred to Pipeline CRM, helping your sales team manage and follow up on leads efficiently.

***

### Benefits of Pipeline CRM Integration

* 🔄 Automatically transfers chatbot leads to Pipeline CRM
* ⚡ Eliminates manual lead entry and reduces operational effort
* 🎯 Ensures sales teams receive lead information instantly
* 📈 Improves lead response times and conversion opportunities
* 🤝 Keeps customer information organized in one central CRM

***

### When should you use this?

Use this integration when:

* You want to automatically send chatbot leads to Pipeline CRM
* You need your sales team to receive enquiries instantly without manual data entry
* You are trying to capture website chatbot leads and assign them directly to your Pipeline CRM workflow

***

### Expected Outcome

After setting this up:

* Pipeline CRM will be successfully connected to BotPenguin
* Lead information collected by your chatbot will automatically appear in Pipeline CRM
* Your sales team will be able to manage and follow up with leads without manual data transfer

{% hint style="info" %}
Use the Test Lead feature after setup to verify that lead data is reaching Pipeline CRM correctly.
{% endhint %}

***

### 🔐 Prerequisites

Before setting up this integration, ensure you have:

* An active Pipeline CRM account
* Access to Account Settings in Pipeline CRM
* API Key enabled within Pipeline CRM
* APP Key generated through Pipeline CRM API Integrations
* A BotPenguin website chatbot flow configured to collect lead information

{% hint style="warning" %}
Missing prerequisites may prevent the integration from connecting successfully.
{% endhint %}

***

### How to Use Pipeline CRM Integration

#### Part A: Connect Pipeline CRM

1. Navigate to "Third Party Integration" under the Chatbot section.

<figure><img src="/files/z1coddjnrti1UELGyUcW" alt=""><figcaption></figcaption></figure>

2. Search for "Pipeline" and click "Connect".

<figure><img src="/files/5qyl1FNkMi898qfFbX2p" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You may see Onpipeline, Pipedrive CRM, and Pipeline. Select **Pipeline** specifically.
{% endhint %}

3. Click "Connect" on the Pipeline Integration page.

<figure><img src="/files/MUs18VDBKvnOzTZTmG9d" alt=""><figcaption></figcaption></figure>

#### Part B: Generate API Credentials in Pipeline CRM

4. Log in to your Pipeline CRM account.

<figure><img src="/files/2s7BqWKfvrXpdoFbL1pe" alt=""><figcaption></figcaption></figure>

5. Navigate to Settings → API → API Integrations.

<figure><img src="/files/7xIH4E1AHN9SCa1bPxdE" alt=""><figcaption></figcaption></figure>

6. Click "+ Add Integration".

<figure><img src="/files/qFYOh1143qlP5PLNzYxP" alt=""><figcaption></figcaption></figure>

7. Complete the required fields:
   1. Application Name
   2. Owner Name
   3. Owner Email
   4. Owner Phone
   5. Authentication Strategy
   6. JWT Expiration Period (if applicable)
   7. Public / Private Selection

<figure><img src="/files/A4E8LzDfLwMIzTnB3vhV" alt=""><figcaption></figcaption></figure>

8. Click "Create API Integration".
9. Copy the generated API Key.
10. Change the integration status from Draft to Submitted.
11. Navigate to API Keys.
12. If API access is disabled, enter your Technical Contact Email and click "Enable API Access".
13. Copy the generated API Key.

#### Part C: Configure the Integration in BotPenguin

14. Return to BotPenguin and enter the API Key and APP Key.

<figure><img src="/files/FWvMtd4XY9ZuQTVNtkEN" alt=""><figcaption></figcaption></figure>

15. Click "Connect".
16. Map chatbot questions to Pipeline CRM fields.

{% hint style="info" %}
Example:

* Name → Name
* Phone Number → PhoneNumber
  {% endhint %}

17. Click "+ Add Parameters" to map additional fields.
18. Click "Save".

{% hint style="success" %}
You are now successfully integrated with Pipedrive CRM!
{% endhint %}

***

### 🔄 How Data Flows (Important)

* BotPenguin collects lead information through chatbot conversations
* Once the conversation is completed, BotPenguin sends mapped lead data to Pipeline CRM
* Pipeline CRM creates a new lead/contact record
* Your sales team can immediately access and follow up on the lead

***

### ⚙️ Configuration Options

* **API Key**: Authenticates the connection with Pipeline CRM
* **APP Key**: Identifies the specific API integration created in Pipeline CRM
* **Question Mapping**: Maps chatbot responses to Pipeline CRM contact fields
* **Test Lead**: Sends a sample lead to verify successful integration

***

### 🚫 Limitations

* Currently supported only for Website Chatbots
* Only mapped fields are transferred to Pipeline CRM
* Contacts are created only after the chatbot flow is completed
* Draft API Integrations in Pipeline CRM cannot authenticate successfully

***

### Best Practices

> 💡 Always map Name, Email, and Phone Number for better lead management.

> ⚠️ Change the API Integration status from Draft to Submitted before connecting.

> 🚀 Use Test Lead immediately after setup to validate data flow.

> 🎯 Use clear integration names such as "BotPenguin Integration" for easier management.

***

### Troubleshooting

<details>

<summary>Chatbot conversation completes but no lead appears in Pipeline CRM</summary>

**Solution:** Ensure the **Default Flow** is enabled, chatbot fields are mapped correctly, and the Pipeline API Integration status is set to **Submitted**.

</details>

<details>

<summary>API Key or APP Key is not accepted</summary>

**Solution:** Verify that both keys were copied correctly from Pipeline CRM without extra spaces and confirm that the API Integration status is **Submitted**.

</details>

<details>

<summary>Unable to locate the API section in Pipeline CRM</summary>

**Solution:** Navigate to **Account Settings** and open the **API** tab from the top navigation menu.

</details>

<details>

<summary>API access is disabled</summary>

**Solution:** Enter a valid **Technical Contact Email** and click **Enable API Access** to generate your API Key.

</details>

<details>

<summary>Contact is created but important fields are empty</summary>

**Solution:** Verify that chatbot questions are mapped to the correct Pipeline CRM parameters (e.g., Name, PhoneNumber) and save the integration again before testing.

</details>

***

### FAQs

<details>

<summary>What is Pipeline CRM Integration in BotPenguin?</summary>

It connects your BotPenguin website chatbot to Pipeline CRM and automatically creates leads when chatbot conversations are completed.

</details>

<details>

<summary>Do I need a Pipeline CRM account to use this integration?</summary>

Yes. An active Pipeline CRM account is required to generate API credentials and connect the integration.

</details>

<details>

<summary>Which chatbot types support this integration?</summary>

Currently, Pipeline CRM Integration is available for Website Chatbots.

</details>

<details>

<summary>What data is transferred to Pipeline CRM?</summary>

Only the fields you map during setup are transferred, such as Name, Email, and Phone Number.

</details>

<details>

<summary>What happens if a user leaves before completing the chatbot flow?</summary>

No lead is created. Only completed chatbot conversations trigger lead creation.

</details>

<details>

<summary>Can I test the integration before going live?</summary>

Yes. Use the Test Lead feature within BotPenguin to send a sample lead to Pipeline CRM.

</details>

<details>

<summary>Can I use the same Pipeline CRM account with multiple bots?</summary>

Yes. The same API credentials can be used across multiple bots by configuring the integration separately for each one.

</details>

<details>

<summary>Where do leads appear in Pipeline CRM?</summary>

Leads appear in the People section of your Pipeline CRM dashboard as new contact records.

</details>

***

### Related Articles

{% content-ref url="/pages/csiixZSVstiKVMrWcI0f" %}
[Website Chatbot Setup and installation](/bots/website-mobile-app-bot/website-chatbot-setup-and-installation.md)
{% endcontent-ref %}

***

### Support

If you still have questions for our team, write to us at **<support@botpenguin.com>**. We’ll get back to you within 48 hours.

***

### 🎉 Completion

🎉 Congratulations, you have successfully set up the Pipeline CRM Integration! Your chatbot leads will now flow automatically into Pipeline CRM, helping your sales team respond faster and manage leads more effectively.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.botpenguin.com/bots/website-mobile-app-bot/3rd-party-integrations/botpenguin-integrations/integrate-botpenguin-with-pipeline.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.