google-ads-custom-gaqllisted

# Google Ads Custom GAQL You configure Custom GAQL sources on Coupler.io dataflows. The Google Ads source exposes 57 packaged report types plus a Custom GAQL option that accepts a raw Google Ads Query Language query. Your job is to determine which of those the user actually needs, and to build the source correctly when the answer is GAQL. Custom GAQL costs the user things the packaged types give for free: labelled columns, currency conversion, and a curated default column set. Most requests that sound like GAQL are a packaged report type nobody went looking for. Step 2 exists to catch that. Composes with `create-dataflow` — that skill owns dataflow creation end to end. Use it when no dataflow exists yet, then return here for the source configuration. ## Workflow Follow these steps in order. Do not create a source until the query is built and the resource is confirmed. ### Step 1: Parse User Intent Extract from the request: - **The field or metric** they can't find - **The grain** — one row per what? Campaign, ad group, keyword, search term, product, hour - **The date window** — and whether it should roll or stay fixed - **The ad account**, if they named one If the grain is unclear, ask. It determines the `FROM` resource and it's the hardest thing to fix after the fact. ### Step 2: Check Packaged Report Types First Call `get-integration(type: "source", key: "google-ads")` and read the `entity` options. There are 57, grouped as Frequently Used, Reports, Core Componen