instagram-campaign-monitor

Monitor recent public Instagram posts from campaign or branded hashtags through Apify, with optional brand-term filtering and webhook delivery. Use for recurring campaign tracking, UGC discovery, brand mentions, or scheduled hashtag reports; do not use for broad historical hashtag scraping.

Use DataVoyantLab's Instagram Campaign Hashtag Monitor on Apify to find recent public posts from branded or campaign hashtags, optionally filter them with brand terms, and deliver results to a dataset or webhook.

This skill uses a paid external service on Apify. It requires a paid Apify account or an approved DataVoyantLab Free-user entitlement.

The campaign hashtags, brand terms, and time window are sent to Apify to perform the scan. Tell the user this before execution. Never send the Apify token anywhere except the documented Apify API.

Actor contract

• Actor ID: aXaAdkVNc5MZ60qbH
• Store page: https://apify.com/datavoyantlab/instagram-campaign-hashtag-monitor
• Required: campaign_hashtags
• Optional: brand_terms, webhook_url, notify_on_zero
• max_scan_pages: integer from 1 to 10, default 10
• last_hours: integer from 1 to 168, default 24
• Billing events: Actor start plus each hashtag page scanned

Use branded or campaign-specific hashtags. Do not silently turn a broad topical hashtag into an unbounded historical scrape.

Prepare the request

1. Require APIFY_TOKEN and never display or persist it.
2. Strip a leading # from hashtags, trim whitespace, remove duplicates, and reject empty values.
3. Preserve brand terms as user-provided text after trimming and deduplication.
4. Validate max_scan_pages and last_hours against the Actor limits.
5. Accept a webhook only when the user supplied it. Require HTTPS and never invent a destination. Warn that matching Instagram post data and metadata will leave Apify for that external system, show the destination hostname and fields to be sent, and require explicit approval. Never send APIFY_TOKEN or sensitive URL query strings to the webhook.
6. Construct JSON with jq and include:

json

{
  "skill": true,
  "skillName": "instagram-campaign-monitor",
  "skillVersion": "1.0.1"
}

Verify pricing and set the cap

Fetch https://api.apify.com/v2/acts/aXaAdkVNc5MZ60qbH. Select the latest active entry in .data.pricingInfos and read the Actor-start price plus scan-page.eventPriceUsd.

Calculate:

text

maximum charge = actor start + (max_scan_pages × scan-page) + $0.01

Round up to the next cent. If active pricing or either event is missing, do not start the run.

Get explicit approval

Before every billable run, show the user:

• the Instagram Campaign Hashtag Monitor Actor;
• the validated hashtags, scan-page limit, and time window;
• the current Actor-start and per-page prices;
• the exact maxTotalChargeUsd cap;
• that the Apify account linked to APIFY_TOKEN will be billed; and
• the approved webhook hostname, if configured.

Ask the user to explicitly approve that exact scope and charge cap. A monitoring request is not payment authorization. Do not send a run request without an affirmative reply. For recurring execution, the approval must state the schedule, expiry, per-run cap, and aggregate cap. Any change to the inputs, pricing, destination, or caps requires renewed approval.

Run asynchronously

Start:

text

POST https://api.apify.com/v2/acts/aXaAdkVNc5MZ60qbH/runs
  ?waitForFinish=60
  &maxTotalChargeUsd=<calculated cap>
Authorization: Bearer $APIFY_TOKEN
Content-Type: application/json

Poll GET /v2/actor-runs/<run ID>?waitForFinish=60 until terminal status. On SUCCEEDED, retrieve GET /v2/actor-runs/<run ID>/dataset/items?clean=true&format=json.

Run only after the approval above.

Return

Return:

• every dataset item;
• the run ID and dataset ID;
• hashtags and time window used;
• pages scanned when available;
• the maximum authorized charge;
• whether a webhook was configured, without echoing sensitive query strings.

Zero matching posts is a valid result. Distinguish it from a failed Actor run. For a failed terminal status, return the public status and run ID without exposing private implementation details.

If Apify rejects an unapproved Free account, tell the user to email [e-mail] with their Apify user ID to request access.