---
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, Slack, Google Forms, webhooks and the data collection level. Which tools it uses, the one step that needs a person, scopes and example prompts."
canonical: "https://linkbreakers.com/help/article/set-up-linkbreakers-integrations-with-an-ai-agent-mcp"
last-updated: 2026-10-30
---

# 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, Slack, Google Forms, webhooks and the data collection level. Which tools it uses, the one step that needs a person, scopes and example prompts.

:::try-ai-prompt {"prompt":"Which integrations are set up on my workspace? Check the retargeting pixels, Slack, Google Forms, 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, Slack, Google Forms, 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.

There is one step an agent cannot do for you. The first time you connect Slack or Google Forms, a person has to approve the connection in a browser. The agent hands you the approval link, you open it once, and from then on the agent configures everything. Retargeting pixels, webhooks and data collection need no approval step at all.

## Quick summary

- Five areas, all available to agents: retargeting pixels, Slack, Google Forms, webhooks, data collection level
- Same operations on every surface: MCP server, Assistant, REST API, CLI and SDKs, all generated from one API
- Slack and Google Forms need a person to approve the first connection in a browser; the agent gives you the link
- Pixels, webhooks and data collection work end to end with no person involved
- 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 Slack or Google Forms 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 |
| Slack | Get the approval link, check the connection, list channels, pick the channel, choose which steps send a message, limit messages to one link, 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 |
| Google Forms | Get the approval link, check the connection, list the Google Forms found on your links and whether the account can read each, pull new responses now, pause or resume, disconnect | `google_forms_oauth_url`, `google_forms_integration_get`, `google_forms_detected_list`, `google_forms_sync`, `google_forms_integration_update`, `google_forms_integration_delete` | Yes, to approve the first connection |
| Webhooks | List, read, create, change, pause, resume and delete webhooks, each with its endpoint, the steps that send it and an optional link filter | `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, the link and the trigger with `slack_integration_update`. It creates the webhook with `webhooks_create`, with the same link and trigger.

Two things to know about this setup:

- Triggers are step kinds, not individual step types. The narrowest choice for form submissions is interaction steps, which covers forms and other steps where the visitor enters something, such as a password
- Slack has one connection per workspace, with one channel and either one link or every link. A webhook also takes one link, so for several trade show links an agent creates one webhook per link

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.

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

### 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 `google_forms_oauth_url`. After you approve, it lists the detected forms with `google_forms_detected_list`, including any the connected Google account cannot read, and runs `google_forms_sync`, which answers with how many responses were synced 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 one step that needs a person

Slack and Google Forms are connected through OAuth: Slack or Google 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` or `google_forms_oauth_url` and gives you the link
2. You open it in a browser where you are signed in to Linkbreakers, and approve in Slack or Google
3. You land back in the Linkbreakers dashboard with the integration connected
4. The agent takes over: channel, triggers, link filter, pause and test for Slack; detected forms, sync and pause for Google Forms

You do this once per workspace. Changing the Slack channel later, pausing it or sending a test 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, Slack, Google Forms | `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 the Slack or Google Forms approval 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)
- **Slack or Google Forms itself**: disconnect it in **Integrations**, or ask the agent to, which removes the connection for every surface

## Limits and caveats

- **Slack and Google Forms need a person once.** The first connection is approved in a browser. An agent can prepare the link, not approve it
- **One Slack connection per workspace.** One channel, and either one link or every link
- **Triggers are step kinds.** Entry, interaction, condition or exit steps, not a single named step
- **Webhooks filter on one link at most.** Use one webhook per link to cover several links, within 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.** `google_forms_detected_list` shows which ones are not accessible
- **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 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 Slack or Google Forms. 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, Slack, Google Forms, webhooks and data collection, checked on 2026-10-30.
- [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-10-30 by Laurent Schaffner.