Link Peeler integrations are built around one rule: external systems can create and consume work, but campaign mutations should still depend on verified row state from desktop link resolution.
Link Peeler integrates with Google Sheets for operator-owned rows, Google Ads Scripts for final URL suffix updates, API Links for signed external job triggers, and platform API mode for hosted row state. The desktop remains the local execution engine across all of those integration paths.
The integrations hub now behaves like a control room: pick the surface that owns source state or trigger work, then route to the page that explains the contract.
Each integration exists to keep one boundary explicit: row ownership, script consumption, signed external work, or hosted state.
Use Google Sheets when operators need reviewable rows, stable row IDs, final URL writeback, and a gradual path into hosted platform state.
Keep offer rows in Sheets while adding desktop resolution, verified writeback, and row identity checks.
Let campaign scripts discover verified state before final URL suffix updates.
Create link fetch work from external systems with HMAC signing, nonce checks, and idempotency.
Use hosted row state and task records when workflows outgrow spreadsheet-only operations.
The specific system changes, but the control boundary stays consistent: source rows enter, the web relay validates and queues, the desktop resolves, and verified state returns.
Select the active source
Use Sheets for operator review or platform API mode for hosted row state.
Create work safely
Start jobs manually, through schedules, or through signed API Links.
Resolve on desktop
The local runtime follows redirects without exposing the desktop inbound.
Store verified state
Final URL, conclusion, failure, and skip state return to the active channel.
Let scripts read state
Google Ads scripts and external systems consume evidence instead of raw guesses.
Thin integration pages list logos. A serious integration hub explains source ownership, execution boundary, failure state, and campaign handoff before a team connects production work.
Sheets keep operator visibility; platform API mode centralizes state when external systems need a durable contract.
Manual runs and schedules can start small; signed API Links add HMAC, nonce, idempotency, and quota checks for external systems.
The desktop pulls outbound and resolves links locally, keeping browser, network, proxy, and device context attached to the evidence.
Google Ads Scripts and internal tools consume verified final URL, conclusion, checked time, and readiness state instead of raw links.
The site now gives each integration its own search-ready page while keeping the architecture easy to understand.
Integration searchers usually arrive with a named tool and an unstated risk. These answers connect each tool to the source, queue, desktop, result, and script boundary it affects.
It integrates with Google Sheets, Google Ads Scripts, API Links, and platform API mode so link operations can move from source rows to desktop evidence and campaign-safe consumption.
Sheets should hold stable row input and receive verified final URL, conclusion, error, skip, checked time, and readiness state after desktop resolution.
Scripts should discover the active channel, read only rows with clean conclusion and readiness state, and keep dry-run logs before suffix mutation.
Use API Links when external systems need to create link fetch work through signed requests, replay controls, idempotency, quotas, and outbound desktop pickup.
Use platform API mode when hosted row state, external triggers, task records, and result contracts matter more than spreadsheet-first operations.
Start with the system that already owns the operational pain: Sheets for row review, Ads Scripts for campaign handoff, API Links for triggers, or platform API for hosted state.
Yes. A team can use Sheets for review, platform API for hosted state, API Links for triggers, and Google Ads Scripts for campaign consumption.
No. Integrations queue or read work through the web service while the desktop pulls work outbound.
Start with Google Sheets if operators already work in spreadsheets. Start with platform API mode if external systems need hosted state from day one.
Production integrations such as API Links and hosted platform mode are Pro surfaces. Free is intended for validation and small workflows.