Authorize offers and creatives
Start a fresh client connection that requeststrackly.offers. Add trackly.agent if the assistant also needs the SMS tools, and trackly.registration for number registration. In Trackly’s consent screen, the owner reviews the Offers and creatives section and accepts it. If the client requests only trackly.agent or trackly.registration, the consent screen still shows Offers and creatives as an optional checkbox; select it to add offer and creative management to that connection.
- An existing
trackly.agentortrackly.registrationconnection does not include offers and creatives. Token refresh cannot add the scope; reconnect and select Offers and creatives on the consent screen. - Private API-key MCP connections cannot use these tools.
- The reviewer demo does not support them.
insufficient_scope with reconnection guidance and makes no request to Trackly.
Activation sends without further approval
An active offer or creative is eligible for scheduled and automated sends with no further approval. Activating an offer also resumes journeys that were auto-paused because of it, and pausing or archiving an offer auto-pauses journeys that can no longer send. Ask the assistant to create records withstatus: "paused", review them with you, and activate them only after you confirm. Both create tools default to active when no status is given.
Tools
The tools call the Offers and Creatives endpoints of the v2 API, so field names and validation match the API reference.
Creative links
Each{{linkN}} placeholder in a creative’s message needs an offer_links entry with exactly one of offer_id or custom_url. On update, offer_links replaces every existing mapping. Messages are checked against blocked-content rules.
Send dates
Offers and creatives accept the same send-date fields:
On update,
null clears a date and an omitted field keeps its value. An end date before the start date returns invalid_date_window. Send dates never change a record’s status. See Send Dates for how they apply to each send path.
Uncertain outcomes
If Trackly’s response to a create, update, or archive is missing or doesn’t confirm the requested change, the tool returns anunknown_* code (for example unknown_offer_create or unknown_creative_archive). The assistant should read the record back, or list records after a create, before doing anything else. Creation is not idempotent, so the assistant must never repeat a create automatically.
Validation errors such as invalid_date_window are returned unchanged. The assistant should correct the input and ask you before trying again.