Windsor.ai Instagram

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

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.

Windsor.ai: Execute a write action on a connector account. Runs an action id from list_actions against an account id from get_connectors, with params matching the action's JSON schema. This modifies external platform state — confirm intent with the user before invoking.

Get the URL to connect or authorize the instagram connector. Returns a browser URL to set up instagram (OAuth or manual credentials), with an auto-login token so the user is signed in automatically. 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 instagram connector. Returns the auth type, an auto-login connect_url to grant access, and (for manual connectors) the credential fields instagram 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: Retrieve data from the instagram 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 auto-login 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.

Windsor.ai: List the scheduled export tasks the user has created. A destination task is a recurring export of a connector's data to a destination. Each entry reports its id, destination type and name, alias, source connector, schedule, and status (active, paused, or deactivated), plus a manage_url to open it in the dashboard. Use this when the user asks what exports, syncs, or destination tasks they already have, or before creating one to avoid duplicates.