> For the complete documentation index, see [llms.txt](https://polser.gitbook.io/polser-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polser.gitbook.io/polser-docs/admin/integrations.md).

# Integrations

{% @arcade/embed flowId="lrd1jYt93gM6KYpixEei" url="<https://app.arcade.software/share/lrd1jYt93gM6KYpixEei>" %}

In addition to our mandatory native integration with **WhatsApp** for using Polser, we also enable you to connect workflow tools through our **Webhook** technology, as well as integrations with **Zapier** and Microsoft's **Power Automate**. This allows you to leverage the workflow tools you are already using and are familiar with.

If you configure any integration, Polser will send any incoming and outgoing event from Meta to the URLs provided on each integration settings page.

<figure><img src="/files/snfFgEhJ1POqiVOEmKfE" alt="" width="563"><figcaption><p>Zapier URL configuration</p></figcaption></figure>

These are standard events from Meta. You can see the payload you can except depending on the event triggered in the [official Meta documentation](https://developers.facebook.com/docs/whatsapp/cloud-api/webhooks/payload-examples). Polser will add additional user information to the event where available so that you can leverage those additional datapoints in your third party integration platforms.

\
Please don't hesitate to let us know which ones you are missing directly on your Integrations page in Polser by clicking the "**Missing an integrations?**"  link.

### Embedded conversation

Polser provides a way for customers to embed a single conversation view into their third-party tools, such as their CRM. The conversation view can be loaded by providing a direct URL to the contact's phone number, following this format:

```

https://your-polser-account.polser.app/conversation/contact-phone-number
```

For example, <https://demo.polser.app/conversation/447822001881>.

The embedded conversation view will appear as follows:

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

In CRM integrations where an open conversation involves a contact with no chat history or record, Polser will not have a name or surname for that user, which only appear when a new chat begins. In this scenario, the UI will display their phone number instead of a username.&#x20;

To prevent this UI issue, we offer a specific URL structure that utilizes parameters to replace the UI name and surname placeholders:

```
https://your-polser-account.polser.app/conversation#phone=3466666666&firstName=Jane&lastName=Doe
```

For example, <https://demo.polser.app/conversation#phone=3466666666\\&firstName=John\\&lastName=Doe>

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

As shown in the image above, the name is inserted via URL parameters when opening this window. Please note there is also an icon that lets you start a new chat with this person.

***

{% hint style="success" %}
Integrations are available through the web application within Polser.
{% endhint %}