> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/integrations-and-data-ingestion/how-to-integrate-with/buzzmonitor.md).

# BuzzMonitor

### Overview

Birdie's BuzzMonitor integration enables users to import social interactions (posts, comments and DMs) straight from the BuzzMonitor API. Below are the key steps to setting up the integration so Birdie can pull data from your environment.

### Requirements

* **BuzzMonitor user**: The user e-mail address tied with the BuzzMonitor platform. (called `bm_user`)
* **BuzzMonitor API Key**: A random unique key generated by BuzzMonitor that authenticates and allows communication between the platform and external systems. (called `api_key`)
* **Platforms sources**: The platforms sources are included in the payload as `report_source` and are used to filter specific platforms and pages, defining which platform(s) the connector will request data from and which page(s) the data is linked to.

The documentation for the **BuzzMonitor API** is private and requires special access. You will need to contact the BuzzMonitor team and request the access.

### Setup in BuzzMonitor

For Birdie to be able to access the **BuzzMonitor API**, you’ll need to contact the BuzzMonitor team and request a **payload** containing all the required information, including authentication details.

{% hint style="warning" %}
The BuzzMonitor team may provide the payload for specific requirements (for example: filter only social media posts and comments, or filter only social media private conversations). The Birdie connector is configured to ignore all filters — we will handle all types of interactions.
{% endhint %}

The payload is in JSON format and should look something like this (this example contains the minimum required fields to work with the BuzzMonitor API):

{% code title="buzzmonitor\_payload.json" %}

```json
{
  "authentication_params": {
    "bm_user": "...",
    "api_key": "..."
  },
  "general_params": {
    "timezone": "-3.0",
    "until": "20250821595959",
    "since": "20250821000000",
    "services": [
      "facebook"
    ]
  },
  "report_sources": {
    "facebook_pages_wall": [
      {
        "name": "...",
        "user": "...",
        "other_pages": false,
        "page_id": "...",
        "source": "..."
      }
    ],
    "instagram": [
      {
        "name": "...",
        "user": "...",
        "bm_user": "..."
      }
    ]
  }
}
```

{% endcode %}

{% hint style="warning" %}
The payload may contain more information; this example contains the minimum required fields to work with the BuzzMonitor API.
{% endhint %}

### Data in scope

#### Sources

The connector currently supports:

* `facebook_private_messages` (DMs)
* `facebook_page_wall` (Posts and Comments)
* `instagram` (DMs, posts and comments)
* `linkedin_updates` (Posts, comments and mentions)

#### Source fields

Each source requires different fields. The only common field is `name`, which is required for all types of source.

* facebook (page\_wall and private\_messages)
  * `name`
  * `user`
  * `page_id`
  * `other_pages`
* instagram
  * `name`
  * `user`
  * `bm_user`
* linkedin
  * `name`

#### Interaction types

The BuzzMonitor platform supports these interaction types:

* Public interactions:
  * `post`
  * `comment`
  * `comment_reply`
  * `reply`
  * `mention`
  * `comment_from_mention`
  * `reels`
  * `ad` (Promoted posts)
  * `carousel_album` (Instagram carousel)
* Private interactions (DMs):
  * `direct_message`
  * `message`

### Connect to Birdie

Through this integration, you can import social media (posts and comments) and conversations (direct messages/inbox).

For each interaction, we extract the main fields for that interaction, such as Channel, Status, Priority, Tags, Author Name, Text, etc.


---

# 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:

```
GET https://ask.birdie.ai/integrations-and-data-ingestion/how-to-integrate-with/buzzmonitor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.