Linkbreakers
Analytics & DataCreate and manage branded short links, QR codes, and vCard contact cards in Linkbreakers, organized by directories and tags. Agents mint trackable assets per campaign and follow the visitor events they produce.
What This Integration Enables
Most short link platforms end at a redirect. Linkbreakers goes one step further in a direction that changes the stakes: Create Contact Card Link publishes a vCard. Behind the code is not a landing page but a person, with their name, job title, organization, email, phone (optionally flagged as a WhatsApp number), postal address and social profiles, downloadable by anyone who scans. That is a real capability for event badges, printed cards and sales teams, and it is also the reason this connector deserves more care than a link shortener normally gets.
The second distinctive surface is identity. Linkbreakers tracks visitors as first-class records, not just as click counts. Identify Visitor takes the lbid value carried by a tracked link and attaches an identity to whoever scanned it, promoting an anonymous visitor into a named profile and merging duplicate records so devices and events converge on one source of truth. List Visitors and List Events return the resulting profiles and the full scan, click and workflow timeline, as JSON or as CSV for reporting. Delete Visitor exists specifically so a deletion request can be honoured. Around all of that sits ordinary link management: create, update and delete links on custom domains, check slug availability, generate a guaranteed-free random slug, organize with nested directories and tags, and register webhooks scoped to specific links and workflow step kinds.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Turning booth scans into named prospects
An event code is printed on the stand and on the handout. Every scan produces an anonymous visitor with a device and an event timeline. When someone completes the follow-up form, the agent calls Identify Visitor with the lbid value the tracked link carried and the email, first name and last name from the submission, plus custom attributes for the session they attended. Anonymous scans from that device retroactively belong to a named person, and if that person already existed in the workspace the two records merge. The agent then syncs the profile and its event history into HubSpot so the rep sees which asset the prospect scanned before the conversation, not after it.
A card fleet that tracks the roster
Field teams change. The agent watches the roster, and for each addition it generates or verifies a slug, publishes a contact card on the company domain, files it in the region's directory and tags it with the territory. For departures, a second flow moves the card's fallback destination to the team page so a scanned card from an old batch still lands somewhere sensible rather than nowhere. List Links filtered by directory gives operations a live inventory of which cards exist for which region, hydrated with signed QR image URLs when a reprint is needed.
Honouring a data deletion request
A request arrives to remove someone's data. The agent searches List Visitors by exact email, retrieves the matching profile with Get Visitor including its devices, events and links, and assembles a summary of everything the workspace holds on that person. Delete Visitor removes the profile and every stored attribute permanently. The agent does not run that call on a match alone, because a fuzzy name match and a real identity are not the same thing.
Human-in-Loop Highlight
The gate on this connector is the contact card, because publishing one is publishing a person's details to anyone who scans a code. Create Contact Card Link accepts a mobile number that can be flagged for WhatsApp and a full postal address, and it serves them as a downloadable vCard with no gate of its own. So before the agent publishes, it renders the card exactly as a scanner would receive it and asks the person whose card it is, in Slack: "Your card at go.company.com/j-reyes will publish your mobile number flagged for WhatsApp and your home-office postal address to anyone who scans your badge. Publish as shown, drop the mobile and keep only the desk line, or drop the address?" The rep answers in the channel and the agent publishes the version they chose. The same discipline covers Delete Visitor, where a permanent removal of a profile is confirmed against a verified identity rather than a fuzzy match, and Identify Visitor, where merging two profiles into one cannot be split back apart afterwards. FlowRunner's connectors are verified against each vendor's official API, so the agent knows precisely which fields a call will make public. Knowing which of those fields a specific person is willing to publish is not an API question, and that is exactly where the agent stops.
Agent Capabilities
20 actionsLinks
5- List Links Retrieves a paginated list of the shortened links in the workspace, with text search over name and shortlink, filtering by tags or directory, sorting by several fields, and hydration of related resources including signed QR code image URLs.
- Get Link Retrieves a single link by ID with its metadata, shortlink, entrypoint URL, directory, lifetime event count and timestamps, optionally hydrating tags, custom domain, page theme, QR design and a signed QR image URL.
- Create Link Creates a shortened link for a destination URL, which is scanned for malicious content first. Supports a supplied or generated slug, a custom domain, a directory, tags created on demand, up to 50 metadata key-value pairs, a fallback destination and conversion tracking.
- Update Link Applies a partial update: rename, change the fallback destination, move between directories, replace or clear tags, change the QR template or page theme, and update the lead goal and lead target definitions used for scoring.
- Delete Link Permanently removes a link from the workspace. The shortlink stops resolving immediately and the operation cannot be undone.
Contact Cards
1- Create Contact Card Link Creates a vCard contact card link serving downloadable contact details when scanned or opened. Accepts name, job title, organization, email, phone (optionally flagged as WhatsApp), website, postal address and social profiles, plus a call to action button label, a custom shortlink, a custom domain, tags, metadata and a fallback URL for devices that cannot download vCards.
Slug Availability
2- Check Shortlink Availability Checks whether a slug is free before creating a link, covering both existing slugs and reserved shortlink IDs, and scopable to a specific custom domain so the same slug can be reused across domains.
- Generate Random Shortlink Generates a random slug guaranteed to be available. Used when the slug needs to be displayed or stored before the link itself is created.
Visitors and Identity
5- List Visitors Retrieves a paginated collection of tracked visitors with an exact email filter, fuzzy search, filtering by the link a visitor interacted with, several sort options and hydration of devices, events and links. Returns JSON or a CSV payload for reporting exports.
- Get Visitor Retrieves one visitor profile by ID with identity fields, custom attributes and aggregate counts for visits, devices and QR codes, optionally hydrating attributed devices, event history and the links they touched.
- Identify Visitor Attaches an identity to a visitor captured from a scan or click using the lbid value the tracked link carried. Anonymous visitors become identified profiles, and a match against an existing visitor merges both records so devices and events converge.
- Update Visitor Applies a partial update to a visitor profile, writing reserved identity fields and custom attributes while leaving anything omitted unchanged.
- Delete Visitor Permanently removes a visitor profile and all of its stored attributes. Used to honour data deletion requests. The operation cannot be undone.
Events and Reporting
1- List Events Retrieves the workspace event timeline of scans, clicks and workflow actions, filterable by link, visitor and date window, with hydration of visitor, device, link, workspace and lead score records, exportable as CSV. History depth is capped by plan and out of range start dates are clamped.
Directories and Tags
3- List Directories Retrieves the directories used to organise links, returning immediate children of a parent or the root level, with a recursive option for a flat list of every descendant.
- Create Directory Creates a directory for organising links, nested under a parent or at the root level. Returns the created directory including its full path.
- List Tags Retrieves the tags defined in the workspace, optionally filtered by name, with cursor pagination. Used to discover the tag names available for filtering or tagging.
Webhooks
3- List Webhooks Retrieves the registered webhook endpoints with their URL, the link and workflow step kinds they are scoped to, delivery counters and the timestamps of the last send and last success. Useful for auditing an integration that has started failing.
- Create Webhook Registers an endpoint that receives a notification whenever a workflow step completes, scoped to one link or to every link in the workspace, and narrowed to specific step kinds such as entry, exit, interaction or condition.
- Delete Webhook Removes a webhook endpoint so it stops receiving notifications. The endpoint must be registered again to resume deliveries.
Frequently Asked Questions
What can FlowRunner do with Linkbreakers?
FlowRunner agents can run List Links, Get Link, and Create Link in Linkbreakers, plus 17 more actions.
Does connecting Linkbreakers to FlowRunner require OAuth?
No. Linkbreakers connects to FlowRunner with an API key, no OAuth flow required.
Can Linkbreakers trigger a FlowRunner workflow automatically?
Linkbreakers doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Linkbreakers
$100 in credits. No card required. Connect in minutes.