← Instagram by Windsor.aiCONTENT HISTORY

Update to Instagram by Windsor.ai

Snapshot Oct 29, 2026 · 12:05 UTC · version 1.0.1

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for instagram

Full description — Now says: It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Instagram by Windsor.ai and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Sep 30, 2026 · 22:48 UTC

After

Oct 29, 2026 · 12:05 UTC

It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact change.

Skill instructions

Before

Sep 30, 2026 · 22:48 UTC

Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics. This connector is for **organic** Instagram analytics only — profile and media insights. It has **no ad or cost data...

After

Oct 29, 2026 · 12:05 UTC

It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact change. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connecto...

Supporting files

Before

Sep 30, 2026 · 22:48 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":462}]

After

Oct 29, 2026 · 12:05 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":511}]

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,6 +1,6 @@
 ---
 name: instagram
-description: Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics.
+description: Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact change. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics.
 ---
 
 # Instagram (organic) via Windsor.ai
@@ -10,17 +10,22 @@
 scoped, so you usually do not need to pass it; when a tool asks for a connector,
 use `instagram`.
 
-This connector is for **organic** Instagram analytics only — profile and media
-insights. It has **no ad or cost data** (Instagram Ads live in the Meta/Facebook
-Ads connector, so route ad-spend questions there), and **publishing is not
-currently enabled**, so treat it as read-only: if the user asks to post or
-publish, tell them that isn't available here rather than attempting it.
+This connector covers **organic** Instagram: profile and media insights, plus
+publishing and comment moderation. It has **no ad or cost data** (Instagram Ads
+live in the Meta/Facebook Ads connector, so route ad-spend questions there).
+Write actions today are `create_image_post`, `create_carousel_post`,
+`create_video_post`, `create_story`, `create_comment`, `reply_to_comment`,
+`hide_comment`, `unhide_comment` and `delete_comment`; the live set is whatever
+`list_actions` returns.
 
 Golden rules:
 
 - **Never guess field, account, or option names** — get them from `get_fields`,
   `get_connectors`, and `get_options`. Call those first.
-- This connector is read-only; there are no live write actions to run.
+- **Publishing and comment changes are public and immediate.** Show the exact
+  caption, media URLs, or reply text and call `execute_action` only after an
+  explicit yes. `delete_comment` cannot be undone; prefer `hide_comment` unless
+  the user asks to delete.
 - Report what the user asked for, concisely.
 
 ## 1. Ground yourself first
@@ -55,7 +60,24 @@
 If a metric the user wants isn't in `get_fields`, say so rather than
 substituting a different one. There is no cost/spend data here.
 
-## 3. Reference real data, don't fabricate
+## 3. Publishing and moderating comments
+
+1. Call `get_connectors` to pick the account; ask if several are connected.
+2. Call `list_actions` for `instagram` and build the params from the returned
+   schema. Media must be publicly reachable URLs (images JPEG, videos MP4 or
+   MOV); a carousel takes 2 to 10 images; a story takes exactly one image or
+   video. Comment actions need a `media_id` or `comment_id` from a `get_data`
+   read, never a guessed id.
+3. Show the post or the comment change in full, exactly as it will appear, and
+   wait for an explicit yes. Never publish placeholder text.
+4. Call `execute_action` once and report the result from the tool, including
+   any media or comment id it returns.
+5. If commenting is refused with a permission error, the account was connected
+   before comment access was added: ask the user to reconnect it with
+   `get_connector_authorization_url`. If write actions are not enabled for the
+   account, send the user to https://onboard.windsor.ai/app/settings/account.
+
+## 4. Reference real data, don't fabricate
 
 On an error (unknown field/connector/account), call the relevant discovery tool
 and retry with correct values or report the specific error. Never invent
Full technical diff · 3 changed fields

changed /description

BEFORE
"Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics."
AFTER
"Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact change. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics."

changed /included_files

BEFORE
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 462
  }
]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 511
  }
]

changed /skill_md_contents

BEFORE
"---\nname: instagram\ndescription: Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics.\n---\n\n# Instagram (organic) via Windsor.ai\n\nWindsor.ai pulls Instagram **organic** insights from the Instagram Graph API. The\nconnector id is `instagram`. On the Instagram app the connector is already\nscoped, so you usually do not need to pass it; when a tool asks for a connector,\nuse `instagram`.\n\nThis connector is for **organic** Instagram analytics only — profile and media\ninsights. It has **no ad or cost data** (Instagram Ads live in the Meta/Facebook\nAds connector, so route ad-spend questions there), and **publishing is not\ncurrently enabled**, so treat it as read-only: if the user asks to post or\npublish, tell them that isn't available here rather than attempting it.\n\nGolden rules:\n\n- **Never guess field, account, or option names** — get them from `get_fields`,\n  `get_connectors`, and `get_options`. Call those first.\n- This connector is read-only; there are no live write actions to run.\n- Report what the user asked for, concisely.\n\n## 1. Ground yourself first\n\nCall `get_connectors` to see which Instagram accounts are connected (each has an\nid and usually a name/username). The account must be an Instagram Professional\naccount (Business or Creator) linked to a Facebook Page. If none is connected,\nhelp the user connect: `get_connector_authorization_url` (or\n`get_connector_connect_info` for the auth type and steps) and give them the\nsetup link — don't describe manual dashboard navigation.\n\nIf several accounts are connected and the request is ambiguous, ask which one.\n\n## 2. Reading insights\n\n1. Call `get_fields` for `instagram` to get valid field ids. Typical ones\n   include account-level metrics (e.g. `followers_count`, `follows_count`,\n   `media_count`, reach, impressions, profile/website clicks, engagement) and\n   per-media metrics — use the exact ids returned, not these examples.\n2. Call `get_data` with `fields`, the target `account`(s), and a date range\n   (`date_from`/`date_to` or a `date_preset` like `last_7d`, `last_30d`,\n   `this_month`; append `T` to include today).\n\nInstagram date behaviour to keep in mind:\n\n- **Lifetime metrics** (e.g. total followers) ignore the date range — the API\n  always returns the latest value. Don't present them as period-specific.\n- **Daily metrics** are only available for roughly the **last 30 days**. Requests\n  for older daily data will return nothing.\n- **Stories** insights exist only for the **last 24 hours**.\n\nIf a metric the user wants isn't in `get_fields`, say so rather than\nsubstituting a different one. There is no cost/spend data here.\n\n## 3. Reference real data, don't fabricate\n\nOn an error (unknown field/connector/account), call the relevant discovery tool\nand retry with correct values or report the specific error. Never invent\nfollower counts, engagement numbers, or media ids.\n"
AFTER
"---\nname: instagram\ndescription: Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact change. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics.\n---\n\n# Instagram (organic) via Windsor.ai\n\nWindsor.ai pulls Instagram **organic** insights from the Instagram Graph API. The\nconnector id is `instagram`. On the Instagram app the connector is already\nscoped, so you usually do not need to pass it; when a tool asks for a connector,\nuse `instagram`.\n\nThis connector covers **organic** Instagram: profile and media insights, plus\npublishing and comment moderation. It has **no ad or cost data** (Instagram Ads\nlive in the Meta/Facebook Ads connector, so route ad-spend questions there).\nWrite actions today are `create_image_post`, `create_carousel_post`,\n`create_video_post`, `create_story`, `create_comment`, `reply_to_comment`,\n`hide_comment`, `unhide_comment` and `delete_comment`; the live set is whatever\n`list_actions` returns.\n\nGolden rules:\n\n- **Never guess field, account, or option names** — get them from `get_fields`,\n  `get_connectors`, and `get_options`. Call those first.\n- **Publishing and comment changes are public and immediate.** Show the exact\n  caption, media URLs, or reply text and call `execute_action` only after an\n  explicit yes. `delete_comment` cannot be undone; prefer `hide_comment` unless\n  the user asks to delete.\n- Report what the user asked for, concisely.\n\n## 1. Ground yourself first\n\nCall `get_connectors` to see which Instagram accounts are connected (each has an\nid and usually a name/username). The account must be an Instagram Professional\naccount (Business or Creator) linked to a Facebook Page. If none is connected,\nhelp the user connect: `get_connector_authorization_url` (or\n`get_connector_connect_info` for the auth type and steps) and give them the\nsetup link — don't describe manual dashboard navigation.\n\nIf several accounts are connected and the request is ambiguous, ask which one.\n\n## 2. Reading insights\n\n1. Call `get_fields` for `instagram` to get valid field ids. Typical ones\n   include account-level metrics (e.g. `followers_count`, `follows_count`,\n   `media_count`, reach, impressions, profile/website clicks, engagement) and\n   per-media metrics — use the exact ids returned, not these examples.\n2. Call `get_data` with `fields`, the target `account`(s), and a date range\n   (`date_from`/`date_to` or a `date_preset` like `last_7d`, `last_30d`,\n   `this_month`; append `T` to include today).\n\nInstagram date behaviour to keep in mind:\n\n- **Lifetime metrics** (e.g. total followers) ignore the date range — the API\n  always returns the latest value. Don't present them as period-specific.\n- **Daily metrics** are only available for roughly the **last 30 days**. Requests\n  for older daily data will return nothing.\n- **Stories** insights exist only for the **last 24 hours**.\n\nIf a metric the user wants isn't in `get_fields`, say so rather than\nsubstituting a different one. There is no cost/spend data here.\n\n## 3. Publishing and moderating comments\n\n1. Call `get_connectors` to pick the account; ask if several are connected.\n2. Call `list_actions` for `instagram` and build the params from the returned\n   schema. Media must be publicly reachable URLs (images JPEG, videos MP4 or\n   MOV); a carousel takes 2 to 10 images; a story takes exactly one image or\n   video. Comment actions need a `media_id` or `comment_id` from a `get_data`\n   read, never a guessed id.\n3. Show the post or the comment change in full, exactly as it will appear, and\n   wait for an explicit yes. Never publish placeholder text.\n4. Call `execute_action` once and report the result from the tool, including\n   any media or comment id it returns.\n5. If commenting is refused with a permission error, the account was connected\n   before comment access was added: ask the user to reconnect it with\n   `get_connector_authorization_url`. If write actions are not enabled for the\n   account, send the user to https://onboard.windsor.ai/app/settings/account.\n\n## 4. Reference real data, don't fabricate\n\nOn an error (unknown field/connector/account), call the relevant discovery tool\nand retry with correct values or report the specific error. Never invent\nfollower counts, engagement numbers, or media ids.\n"
Full snapshot data
{
  "description": "Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact change. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 511
    }
  ],
  "name": "instagram",
  "skill_md_contents": "---\nname: instagram\ndescription: Analyze Instagram organic performance through Windsor.ai. Use when the user asks about their Instagram Business or Creator account's insights — followers, reach, impressions, profile or website clicks, engagement, or the performance of individual media/posts. It can also publish image, carousel, video (Reels) and story posts and reply to, hide, unhide or delete comments, always after the user confirms the exact change. Do not use for Instagram Ads (those live in the Meta/Facebook Ads connector), other platforms, or GA4/website analytics.\n---\n\n# Instagram (organic) via Windsor.ai\n\nWindsor.ai pulls Instagram **organic** insights from the Instagram Graph API. The\nconnector id is `instagram`. On the Instagram app the connector is already\nscoped, so you usually do not need to pass it; when a tool asks for a connector,\nuse `instagram`.\n\nThis connector covers **organic** Instagram: profile and media insights, plus\npublishing and comment moderation. It has **no ad or cost data** (Instagram Ads\nlive in the Meta/Facebook Ads connector, so route ad-spend questions there).\nWrite actions today are `create_image_post`, `create_carousel_post`,\n`create_video_post`, `create_story`, `create_comment`, `reply_to_comment`,\n`hide_comment`, `unhide_comment` and `delete_comment`; the live set is whatever\n`list_actions` returns.\n\nGolden rules:\n\n- **Never guess field, account, or option names** — get them from `get_fields`,\n  `get_connectors`, and `get_options`. Call those first.\n- **Publishing and comment changes are public and immediate.** Show the exact\n  caption, media URLs, or reply text and call `execute_action` only after an\n  explicit yes. `delete_comment` cannot be undone; prefer `hide_comment` unless\n  the user asks to delete.\n- Report what the user asked for, concisely.\n\n## 1. Ground yourself first\n\nCall `get_connectors` to see which Instagram accounts are connected (each has an\nid and usually a name/username). The account must be an Instagram Professional\naccount (Business or Creator) linked to a Facebook Page. If none is connected,\nhelp the user connect: `get_connector_authorization_url` (or\n`get_connector_connect_info` for the auth type and steps) and give them the\nsetup link — don't describe manual dashboard navigation.\n\nIf several accounts are connected and the request is ambiguous, ask which one.\n\n## 2. Reading insights\n\n1. Call `get_fields` for `instagram` to get valid field ids. Typical ones\n   include account-level metrics (e.g. `followers_count`, `follows_count`,\n   `media_count`, reach, impressions, profile/website clicks, engagement) and\n   per-media metrics — use the exact ids returned, not these examples.\n2. Call `get_data` with `fields`, the target `account`(s), and a date range\n   (`date_from`/`date_to` or a `date_preset` like `last_7d`, `last_30d`,\n   `this_month`; append `T` to include today).\n\nInstagram date behaviour to keep in mind:\n\n- **Lifetime metrics** (e.g. total followers) ignore the date range — the API\n  always returns the latest value. Don't present them as period-specific.\n- **Daily metrics** are only available for roughly the **last 30 days**. Requests\n  for older daily data will return nothing.\n- **Stories** insights exist only for the **last 24 hours**.\n\nIf a metric the user wants isn't in `get_fields`, say so rather than\nsubstituting a different one. There is no cost/spend data here.\n\n## 3. Publishing and moderating comments\n\n1. Call `get_connectors` to pick the account; ask if several are connected.\n2. Call `list_actions` for `instagram` and build the params from the returned\n   schema. Media must be publicly reachable URLs (images JPEG, videos MP4 or\n   MOV); a carousel takes 2 to 10 images; a story takes exactly one image or\n   video. Comment actions need a `media_id` or `comment_id` from a `get_data`\n   read, never a guessed id.\n3. Show the post or the comment change in full, exactly as it will appear, and\n   wait for an explicit yes. Never publish placeholder text.\n4. Call `execute_action` once and report the result from the tool, including\n   any media or comment id it returns.\n5. If commenting is refused with a permission error, the account was connected\n   before comment access was added: ask the user to reconnect it with\n   `get_connector_authorization_url`. If write actions are not enabled for the\n   account, send the user to https://onboard.windsor.ai/app/settings/account.\n\n## 4. Reference real data, don't fabricate\n\nOn an error (unknown field/connector/account), call the relevant discovery tool\nand retry with correct values or report the specific error. Never invent\nfollower counts, engagement numbers, or media ids.\n"
}

SHA-256 of public snapshot: fbbd9fd6147367133f72c90eb1cecf5cdd2db5dc65c2972d126215811163f40e