Adako

Create a daily monitor on an ad account

Saves a rule that Adako evaluates once a day against its synced copy of the account — no platform call, no task cost. When the rule holds it emails the operator, and when it carries an action it creates a proposal they can approve. Use when: the user asks to be told about a metric ("alert me if…", "watch…", "let me know when…") and has named a metric, a direction and a number. Do not use when: the user wants a one-off answer about the last few days — read the data instead. Do not create a second monitor for a rule that already exists; call list_monitors first. Returns the monitor, the rule in plain words, and the day it will first be evaluated. Monitors read yesterday in the account's timezone once that day has fully synced (a day later for accounts far behind UTC), compared with a baseline of the previous baseline_days days. A monitor with an action still changes nothing on its own: the action becomes a proposal the user approves. Actions need exactly one campaign id so the proposal names one object, and they run on Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads; a monitor on any other platform emails and proposes nothing. Watching an agency's whole platform: pass all_accounts instead of account_id. One monitor then covers every active account on that platform, each judged on its own numbers and currency, and one email a day lists the accounts that fired. Leave platform out as well and it covers every platform the user has connected. Either way it cannot carry an action or campaign ids, because both name one account. If you are unsure which metric, account or threshold the user means, ask. Never invent a threshold.

post/api/v1/tools/create_monitor/execute

Request

  • Base URL: https://adako.ai
  • URL: https://adako.ai/api/v1/tools/create_monitor/execute
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

Optional 8-128 character key. A successful envelope is cached for 24 hours; replaying the key with the same arguments returns it again with Idempotent-Replayed: true, and replaying it with different arguments answers 409.

Request body

Response

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

successunknown required
toolstring required
dataobject required

Machine-readable result.

markdownstring required

The same result written for a person or a model.

proposal_idstring

Present for writes. Nothing changes on the ad platform until it is approved.

approve_urlstring

Where a person approves the proposal.

request_idstring required

Changes

No recorded changes to this operation across all 1 revision of this API.