Choose the task and the records
Give your agent the asset URL, audience, publisher pages and campaign purpose. Choose the saved AgentLinkOps prospects and matching CRM records. Use agentlinkops-campaigns with the selected prospects, published asset and chosen CRM or sender. Its handoff workflow checks publisher fit, relevant replies and suppression, then prepares drafts and a field-mapping preview with stable record IDs. Missing access produces a portable handoff with unresolved questions. A draft-only handoff sends no message and activates no sequence.Qualify before handing off
Inspect the exact publisher page and record the relevant passage, date and evidence limits. Separate eligible, rejected and unresolved candidates. Campaign research covers audience fit and public contact routes. Review and humanize the draft. Do not invent familiarity, addresses or deliverability. Missing sender access leaves suppression checks unresolved and the handoff unready for sending.Map a portable handoff
Preview the selected rows, stable IDs, fields and changes before writing to your destination. Keep these facts separate: the draft, its delivery and replies, and the observed link. A saved draft does not establish a send or placement. After a write, retain its receipt and read the destination to confirm the intended fields. Follow all result pages needed to find the selected IDs. Report accepted, rejected and unchanged rows separately. A success flag alone does not prove the draft exists.Example handoff and optional toolkit recipe
This example uses fictional records and the toolkit’squalified-campaign-handoff and placement-reconciliation recipes, version 1.0.4, reviewed September 14, 2026. It supplies no vendor import schema or native sender connector.
The optional qualified-campaign-handoff recipe uses supplied publisher records, checks the asset’s publication state and evidence, and prepares reviewed drafts with a destination-mapping preview. Select it through agent setup when you need its detailed checkpoint and recovery procedure. Keep missing facts marked unknown. If access is unavailable, prepare a portable handoff. The recipe sends no messages and activates no sequence.
For a read-only checklist, run
agentlinkops setup --plan --goal prepare-campaign --mode external. It writes nothing and does not execute a skill or recipe. See the setup reference or use the recipe directly.
Preparing supplied inputs needs no AgentLinkOps account. Fresh checks need page access. Hosted operations need account permission and available service access; installing a skill grants neither.
Reconcile a claimed placement
Get the exact publisher page and expected target URL, then check the placement. Read the dated observation; a reply alone is not evidence and an incomplete check stays unknown. Record the outcome on the AgentLinkOps prospect and, if needed, the matching CRM record. Keep earlier observation dates even when a later check is unknown. See evidence states.Several contacts for one publisher placement
Keep one opportunity for the exact publisher page and destination. Preserve its saved reference, saved contact association and monitoring preferences. Each recipient needs their own contact, campaign source record and dated outcomes. A limited operator pilot providessave_campaign_participation and record_campaign_participation_outcome. Use this path only when your authenticated connection lists both commands. Save each recipient against the existing opportunity, then read the returned binding revision before recording their source events. A recipient reply or decline updates that recipient’s progress. Independent link evidence still belongs to the shared opportunity.
If these commands are absent, keep the additional recipient records in your existing CRM and hold their hosted mapping. Do not rotate the opportunity’s saved contact association, duplicate the placement or invent a source URL to import them. Your sender continues to own mailbox access, message bodies, sequences and suppression.