---
title: "Set up every Linkbreakers integration with an AI agent"
description: "An AI agent connected to the Linkbreakers MCP server, or the in-app Assistant, can set up retargeting pixels, Google Analytics 4, Slack, Google Forms, form tools, contact tools such as HubSpot, Mailchimp or Salesforce, webhooks and the data collection level. Which tools it uses, the steps that need a person, scopes and example prompts."
canonical: "https://linkbreakers.com/help/article/set-up-linkbreakers-integrations-with-an-ai-agent-mcp"
last-updated: 2026-11-16
---

# Set up every Linkbreakers integration with an AI agent

> An AI agent connected to the Linkbreakers MCP server, or the in-app Assistant, can set up retargeting pixels, Google Analytics 4, Slack, Google Forms, form tools, contact tools such as HubSpot, Mailchimp or Salesforce, webhooks and the data collection level. Which tools it uses, the steps that need a person, scopes and example prompts.

:::try-ai-prompt {"prompt":"Which integrations are set up on my workspace? Check the retargeting pixels, Google Analytics, Slack, Google Forms, form tools, contact tools, webhooks and the data collection level.","description":"Ask the Assistant what is connected.","target":"assistant"}:::

## Short answer

Yes. Every integration setting in Linkbreakers can be read and changed by an AI agent: retargeting pixels, Google Analytics 4, Slack, the form tools (Google Forms, Typeform, Tally, Jotform, Paperform), the contact tools (Bird, Brevo, MailerLite, Kit, Loops, Mailchimp, Klaviyo, Customer.io, Pipedrive, Freshsales, HubSpot, Salesforce, Zoho CRM), webhooks and the data collection level. An agent connected to the [Linkbreakers MCP server](/help/article/mcp-server-setup), such as Claude or Cursor, or the Assistant inside the dashboard, gets one tool per operation, so you can describe the setup you want in plain words and let the agent do it.

Some first connections need a person. Slack, Google Forms, Salesforce and Zoho CRM are approved by signing in, in a browser: the agent hands you the link, you open it once, and from then on the agent configures everything. Typeform can be approved the same way, or connected on its page under **Integrations**; Tally, Jotform and Paperform are connected by you on their page with an API key. After that, the agent can manage them. Contact tools that use an API key, retargeting pixels, Google Analytics 4, webhooks and data collection need no person at all: the agent connects them with the key you give it.

## Quick summary

- Eight areas, all available to agents: retargeting pixels, Google Analytics 4, Slack, Google Forms, form tools, contact tools, webhooks, data collection level
- Same operations on every surface: MCP server, Assistant, REST API, CLI and SDKs, all generated from one API
- Slack, Google Forms, Salesforce and Zoho CRM need a person to sign in once; the agent gives you the link
- Tally, Jotform and Paperform are connected by a person in the dashboard; the agent manages them after
- Pixels, Google Analytics 4, webhooks, data collection and contact tools with an API key work end to end with no person involved
- Slack, Google Analytics 4, webhooks, contact tools and form tools share the same Where, When and What is sent setting, the `delivery` field
- REST, CLI and SDK tokens can be limited to the scopes the job needs; MCP clients can request scopes through OAuth
- An agent should ask you before disconnecting an integration or deleting a webhook, and the tools tell it to

## What an agent can set up

| Integration | What an agent can do | Tools | Needs a person once? |
|---|---|---|---|
| Retargeting pixels | Read the pixels; set, change or remove the Meta Pixel, Google tag, TikTok Pixel, LinkedIn Insight Tag and Google Tag Manager container. It sends only the pixels to change, and an empty value removes one | `retargeting_pixels_get`, `retargeting_pixels_update` | No |
| Google Analytics 4 | Check the connection, connect a GA4 property with its Measurement ID and Measurement Protocol API secret, change the property, send a test event, disconnect. The secret is never read back | `google_analytics_integration_get`, `google_analytics_integration_update`, `google_analytics_integration_test`, `google_analytics_integration_delete` | No |
| Slack | Get the approval link, check the connection, list channels, pick the channel, choose which links, moments or steps send a message and which visitor data it shows, pause or resume, send a test message, disconnect | `slack_oauth_url`, `slack_integration_get`, `slack_channels_list`, `slack_integration_update`, `slack_integration_test`, `slack_integration_delete` | Yes, to approve the first connection |
| Form tools: Google Forms, Typeform, Tally, Jotform, Paperform | Get the sign-in link for Google Forms or Typeform, check the connection, list the forms found behind your links and whether each is ready, check them again now (for Google Forms this also pulls the new responses), choose the link of a Google Form that is behind several links, choose which links' forms bring answers in and which answers are kept, pause or resume, disconnect | `form_integrations_list`, `form_integration_get`, `form_integration_oauth_url`, `form_integration_forms_list`, `form_integration_forms_prepare`, `form_integration_form_link_choose`, `form_integration_update`, `form_integration_disconnect` | Yes: a person approves the Google or Typeform sign-in, or connects Tally, Jotform and Paperform on their page under **Integrations** |
| Contact tools: Bird, Brevo, MailerLite, Kit, Loops, Mailchimp, Klaviyo, Customer.io, Pipedrive, Freshsales, HubSpot | Connect with the tool's API key (for Freshsales, with its account domain), list its lists, audiences or groups and pick one, list its custom fields and map answers to them, list CRM pipelines and stages, set tags, the consent answer and the record created, choose the delivery setting, test, disconnect | `contact_integrations_list`, `contact_integration_get`, `contact_integration_connect`, `contact_integration_lists`, `contact_integration_fields`, `contact_integration_pipelines`, `contact_integration_update`, `contact_integration_test`, `contact_integration_disconnect` | No |
| Contact tools that sign in: Salesforce, Zoho CRM | The same as above, except connecting: the agent checks how the tool connects with `contact_integration_tool_info` and gets the sign-in link with `contact_integration_oauth_start`. For Salesforce, an admin installs the Linkbreakers package once per org first, from the link `contact_integration_tool_info` gives | `contact_integration_tool_info`, `contact_integration_oauth_start`, and the contact tools above | Yes, to sign in (and, for Salesforce, to install the package) |
| Webhooks | List, read, create, change, pause, resume and delete webhooks, each with its endpoint and which links, moments or steps and visitor data it sends | `webhooks_list`, `webhooks_get`, `webhooks_create`, `webhooks_update`, `webhooks_delete` | No |
| Data collection | Read and set the workspace's level: None, Basic or Advanced. Advanced needs a paid plan, from Light | `data_collection_get`, `data_collection_update` | No |

## Example prompts

Give any of these to an agent connected to the MCP server, or type them into the Assistant.

### Form submissions to Slack and to a CRM webhook

> Send every form submission on my trade show link to #leads in Slack, and send the same submissions to my CRM webhook at https://crm.example.com/hooks/linkbreakers.

The agent checks whether Slack is connected with `slack_integration_get`. If it is not, it calls `slack_oauth_url` and gives you the link to approve. Once Slack is connected, it finds `#leads` with `slack_channels_list`, then sets the channel and the `delivery` field (the link, and the [form step](/workflow-steps/form) or the Interaction moment) with `slack_integration_update`. It creates the webhook with `webhooks_create`, with the same `delivery`.

Two things to know about this setup:

- The `delivery` field is the same Where, When and What is sent as in the dashboard: links, directories and tags; moments or specific steps; and how much visitor data goes out. Sending it replaces the whole setting, so the agent reads it first
- Slack has one connection per workspace, with one channel. One webhook can cover several links, directories or tags

If `#leads` is private, invite the Linkbreakers bot first with `/invite @Linkbreakers` in that channel. `slack_channels_list` shows the agent which channels the bot is already in.

### QR code leads in HubSpot

> Connect HubSpot with my service key pat-eu1-..., add synced contacts to my Trade show leads list and create a deal in the first stage of my Sales pipeline for each one.

The agent calls `contact_integration_connect` with `CONTACT_TOOL_HUBSPOT` and the key, finds the list with `contact_integration_lists` and the pipeline and stage with `contact_integration_pipelines`, then saves them with `contact_integration_update`. `contact_integration_test` confirms the key works and lists the properties form answers can go to. The same tools connect the other contact tools; see the [HubSpot integration guide](/help/article/linkbreakers-hubspot-integration-qr-lead-capture-and-crm-sync) for the scopes the key needs.

### Pixels on every link

> Add my Meta pixel 123456789012345 and my Google tag G-ABC1234 to all my links. Leave the other pixels as they are.

The agent reads the current pixels with `retargeting_pixels_get` and sends one `retargeting_pixels_update` with only those two fields. See the [retargeting pixels guide](/help/article/retargeting-pixels-meta-google-tiktok-linkedin-and-google-tag-manager) for where to find each ID and the short delay pixels add to visits.

### Scans and leads in Google Analytics 4

> Connect Google Analytics with Measurement ID G-ABC123DEF4 and API secret abcDEF123, then send a test event.

The agent calls `google_analytics_integration_update`, then `google_analytics_integration_test`, and tells you to look for `linkbreakers_test` in GA4 DebugView. Google accepts events even with a wrong secret, so DebugView is the real check. From then on, every person's scan, click and form submission reaches GA4 from Linkbreakers' servers, with no personal data. See the [Google Analytics 4 integration guide](/help/article/google-analytics-4-integration-for-qr-codes-and-links) for the events and the custom dimensions to register.

### Advanced data collection

> Switch data collection to Advanced.

The agent calls `data_collection_update`. The level applies to every link of the workspace. On the Free plan the change is refused, because Advanced needs a paid plan. See [what data you can collect from QR code scans](/help/article/what-data-you-can-collect-from-qr-code-scans-location-device-behavior) for what each level records.

### Google Forms responses on visitor profiles

> Connect Google Forms, then tell me which of my links point to a Google Form and sync the responses now.

The agent gives you the approval link from `form_integration_oauth_url` with the tool `GOOGLE_FORMS`. After you approve, it lists the forms found with `form_integration_forms_list`, including any the connected Google account cannot read, and runs `form_integration_forms_prepare`, which pulls the new responses now; `form_integration_get` then shows how many responses came in and how many visitors were enriched. Forms are never set up by hand: they are found from links that redirect to a Google Form.

## How it works

Every integration operation is defined once in the Linkbreakers API. The MCP server tools, the Assistant's tools, the REST endpoints, the CLI commands and the TypeScript, Python, Go, Java and Rust SDKs are all generated from that one definition. An agent therefore has the same options as the dashboard, under the same rules: the same ID checks on pixels, the same plan check on Advanced data collection, the same webhook limits for your plan.

Where an agent runs decides how it connects:

- **MCP server**: add `https://mcp.linkbreakers.com` to your client and sign in with OAuth. Follow the [MCP server setup guide](/help/article/mcp-server-setup) for Claude, Claude Code, Continue and other MCP clients. The MCP server does not accept API tokens
- **Assistant**: open it in the dashboard and ask. It acts with your own session
- **REST API, CLI and SDKs**: use an API token, ideally restricted to the scopes below. A new API operation reaches the CLI and the SDKs with their next release

## The steps that need a person

Slack, Google Forms, Salesforce and Zoho CRM are connected by signing in: the tool asks a person to approve access to their account, and no agent can click that button for you.

1. The agent calls `slack_oauth_url`, `form_integration_oauth_url` (Google Forms or Typeform) or `contact_integration_oauth_start` and gives you the link
2. You open it in a browser where you are signed in to Linkbreakers, and approve in Slack, Google, Typeform, Salesforce or Zoho
3. You land back in the Linkbreakers dashboard with the integration connected
4. The agent takes over: channel, delivery, pause and test for Slack; forms found, sync and pause for Google Forms and Typeform; list, fields, records and delivery for Salesforce and Zoho CRM

For Salesforce, an admin first installs the Linkbreakers package once per org; the agent gives you that link from `contact_integration_tool_info`.

Tally, Jotform and Paperform have no connect tool for agents: open their page under **Integrations** and connect them there with an API key. The agent can then list and prepare the forms, change what comes in, pause or disconnect.

You do this once per workspace. Changing settings later needs no new approval. Disconnecting and connecting again does.

## Security: tokens, scopes and revoking

Each surface uses its own credential:

| Surface | Credential | How to limit it |
|---|---|---|
| MCP server | OAuth sign-in from your MCP client | Request scopes in the OAuth `scope` parameter; without them the grant is full access |
| Assistant | Your dashboard session | Acts as you, in the workspace you have open |
| REST API, CLI, SDKs | API token | Create it as **Restricted** in **Dashboard > API Tokens** |

The scopes each area needs:

| Area | Read | Change |
|---|---|---|
| Retargeting pixels, Google Analytics 4, Slack, Google Forms, form tools, contact tools | `integrations:read` | `integrations:write` |
| Webhooks | `webhooks:read` | `webhooks:write` |
| Data collection level | `links:read` | `links:write` |

A write scope includes the read scope of the same resource. Getting a Slack, Google Forms, Salesforce or Zoho CRM sign-in link needs `integrations:write`. A token that lacks a scope is refused with `403` and `INSUFFICIENT_SCOPE`, naming the scope that was missing. See [API token scopes](/help/article/api-token-scopes) for how to create a restricted token.

To take access away:

- **API token**: revoke it in **Dashboard > API Tokens**, or change its access to fewer scopes
- **MCP client**: sign out of all sessions from **Settings > Security**, which invalidates its OAuth tokens. See [what to do if your account is compromised](/help/article/mcp-server-setup#what-if-my-account-is-compromised)
- **An integration itself**: disconnect it in **Integrations**, or ask the agent to, which removes the connection for every surface

## Limits and caveats

- **Slack, Google Forms, Salesforce and Zoho CRM need a person once.** The first connection is approved in a browser. An agent can prepare the link, not approve it
- **Tally, Jotform and Paperform are connected in the dashboard.** Agents manage them once connected
- **One Slack connection per workspace**, with one channel
- **One connection per contact tool per workspace**, with one list, audience, group or tag
- **Delivery replaces the whole setting.** An agent reads it before changing it, and gives at least one moment or one step
- **Webhooks count toward your plan's webhook limit**
- **Data collection is workspace-wide through these tools.** The level an agent sets applies to every link. Advanced needs a paid plan, from Light
- **Private Slack channels need the bot invited** with `/invite @Linkbreakers` before messages can be posted there
- **Google Forms only syncs forms the connected account can read.** `form_integration_forms_list` shows which ones are not accessible (readiness `FORM_READINESS_NEEDS_ACCESS`)
- **Agents act with the access they are given.** Restrict tokens and OAuth scopes to what the task needs

## Frequently asked questions

### Can an agent connect HubSpot or Mailchimp without me?

Yes, if you give it the API key. Contact tools that use a key are connected with `contact_integration_connect`. Salesforce and Zoho CRM need you to sign in once.

### Can an agent connect Slack without me?

No. Slack asks a person to approve the connection. The agent gets the link with `slack_oauth_url`, you open it and approve, and the agent does the rest.

### Do retargeting pixels or webhooks need an approval step?

No. An agent can add, change or remove pixels, and create or change webhooks, with no person involved.

### Which AI agents work with this?

Any client that supports remote MCP servers, such as Claude, Claude Code or Continue, through the [MCP server](/help/article/mcp-server-setup). Agents that call HTTP APIs can use the REST API, the CLI or an SDK with an API token. The Assistant works inside the dashboard.

### Can an agent delete my webhooks or disconnect Slack?

It can, with a token or session that has the write scope. The tool descriptions tell agents to ask you first before deleting a webhook or disconnecting an integration. To rule it out, give the agent a token with read scopes only.

### Will the agent overwrite pixels I did not mention?

No. A pixel update sends only the pixels to change, and the others keep their value. An empty value removes a pixel.

### Can an agent turn on Advanced data collection on the Free plan?

No. The change is refused on the Free plan, the same as in the dashboard. Advanced is available on paid plans from Light.

## Sources

- Linkbreakers API definitions, MCP tools and Assistant tools for retargeting pixels, Google Analytics 4, Slack, Google Forms, form tools, contact tools, webhooks and data collection, checked on 2026-11-16.
- [Linkbreakers MCP server setup](/help/article/mcp-server-setup)
- [API token scopes](/help/article/api-token-scopes)
- Model Context Protocol specification: https://modelcontextprotocol.io/specification
- Slack, installing with OAuth: https://api.slack.com/authentication/oauth-v2

## Last reviewed

2026-11-16 by Laurent Schaffner.
