Windsor.ai Search Console

Windsor.ai: Send feedback, a support request, or a feature request. Reports a problem, shares feedback, or suggests a feature. Inquiries are recorded in English. Returns a reference ID the user can share with Windsor.ai support.

Windsor.ai: Create a custom (formula) field on a connector. A custom field is a user-defined metric or dimension computed from a connector's existing fields; once created it behaves like a normal field in get_fields, get_data and scheduled exports. Useful for recreating calculated fields when migrating from another platform. Call get_fields first for the connector's valid source field ids, and get_custom_fields to avoid creating a duplicate. This stores configuration in the user's Windsor.ai account — confirm the field with the user before creating it.

Windsor.ai: Create a scheduled export of connector data to a destination. Call get_destinations and get_destination_setup_info first for the destination_type, its target fields and a credential_id, and get_fields for the source field ids. This creates recurring external state — confirm the source, destination target, and schedule with the user before calling. Only works when the destination's create_in_chat is true; otherwise use its setup_url. Never put secrets in config; the user enters those in the dashboard form.

Get the URL to connect or authorize the searchconsole connector. Returns a browser URL to set up searchconsole (OAuth or manual credentials). The user's existing Windsor.ai session signs them in; if it has expired they are asked to sign in first. Use this for connect, grant access, authorize, add, replace, or reconnect requests, including adding another account to this already-connected connector. Do not substitute prose dashboard navigation steps for this link.

Describe how the user grants access to the searchconsole connector. Returns the auth type, a connect_url the user opens to grant access, and (for manual connectors) the credential fields searchconsole requires. Hand the user the connect_url; never ask them to paste secrets into the chat. Use this for connect, grant access, authorize, add, replace, or reconnect requests, including adding another account to this already-connected connector. Do not substitute prose dashboard navigation steps for the connect_url.

Windsor.ai: List connectors, their accounts, write actions, and options. By default returns only connectors that have connected accounts; pass include_not_yet_connected=True for every available connector. Accounts carry an id and, when available, a name. Connectors that support write actions carry an `actions` list of action ids for execute_action. Connectors that expose read options carry an `options` list of option ids that change what a get_data read returns (call get_options for their meaning and values). Covers 350+ sources: advertising (Meta Ads, Google Ads, TikTok Ads, LinkedIn Ads), analytics (Google Analytics 4), CRM and e-commerce (HubSpot, Shopify), payments (Stripe), warehouses (BigQuery, Snowflake), and more.

Windsor.ai: Get the authenticated user's username, email and plan. `plan_id`, `plan_name` and `is_paid` come from the live Windsor.ai profile; they are null when the profile lookup fails, which means the plan is unknown — not that the user is on a free plan.

Windsor.ai: List the user's custom (formula) fields across connectors. A custom field is a user-defined metric or dimension computed from a connector's existing fields with a formula (for example spend times a margin, or a CPA). Each entry reports the connector it belongs to, its field_name, the generated field_id used in get_data/get_fields, its type (NUMERIC or TEXT), and the formula. Call this before create_custom_field to see which fields already exist and avoid creating duplicates.

Windsor.ai: Retrieve data from the searchconsole connector. Call get_fields first — field IDs must come from it. Use all requested days for calculations; always use code for numerical computations.

Windsor.ai: Describe how to set up a scheduled export to a destination. Always call get_destinations first to get the correct destination id. Returns the auth type, the target fields describing where data is written, the allowed schedules, reusable credentials (OAuth or service account), and a setup_url link to the dashboard form. Sensitive fields (service accounts, passwords, keys) are entered by the user in the setup_url form — never ask them to paste secrets into chat. When create_in_chat is true, collect the non-sensitive target fields and call create_destination_task; otherwise hand the user the setup_url.