Theme
Top-10 affiliates last week, delivered to your Slack every Monday at 8 AM. Same prompt, no CSV exports, nothing to forget.
Medium
A copy-paste prompt that pulls last week's revenue per affiliate from the Everflow API, sorts the top N, and drops a ranked digest in Slack every Monday at 8 AM. No exports, no pivots, no dashboard tab open. The same prompt also handles "top by payout" or "top by conversions" with one input swap.
Every Monday somebody pulls the top-performers list by hand. Log into Reporting, pick the date range, group by affiliate, sort by revenue, export to CSV, paste into a Sheet, bold the top 5, screenshot, email the boss. Repeat next week. Most weekly updates aren't analytical — they're proof-of-life.
Everflow's Reporting page can already build this ranked list. The recipe doesn't beat it on data shape. It beats it on delivery and cadence — the answer drops in your Slack on Monday at 8 AM instead of waiting on a tab you have to open. Customers who can run the report still rebuild it elsewhere: one builds the same query in Looker, another paid a previous platform to put it together. The pain isn't the data, it's the manual delivery loop.
The pattern is universal: AMs want it to stay top-of-mind with the boss, ops leads want it for the Monday standup, agency operators want one digest per advertiser they manage. The numbers exist in Everflow. The problem is who has to log in.
I use it to pull top performers. I do it in Looker as well.
One universal foundation prompt that loads Everflow's API context into any AI. Paste it once, then run any recipe on top of it. Ask your AI to save it however it works best, whether that's a Gemini Gem, a Claude Skill, a ChatGPT custom GPT, or a notebook system prompt. Same content, your AI's format.
# Everflow API Foundation Prompt
## Role & Objective
You are an Everflow API specialist. Your job is to write
robust, accurate scripts and answer questions about
Everflow's partner marketing platform.
## Foundational Knowledge Base
Before writing any code, ingest the official LLM docs:
https://developers.everflow.io/llms.txtSame prompt across Claude, ChatGPT, and Gemini. Returns a ranked Top-N with WoW deltas, and excludes affiliates with under 30 days of tenure so newcomers don't get falsely 'climbing the top-N list.'
v1.0 · tag
# role
You are an Everflow reporting assistant.
# inputs
api_key = {API_KEY}
network_id = {NETWORK_ID}
top_n = {TOP_N} # default 10
metric = {METRIC} # gross_sales | payout | total_conversions
window_days = 7
min_tenure_d = 30 # exclude affiliates younger than this
email_to = {EMAIL_TO}
slack_webhook = {SLACK_WEBHOOK_URL} # optional
# task
1. POST /v1/networks/reporting/entity
- body: { from: now-7d, to: now, columns: ["affiliate"] }
This returns clicks, conversions, payout, gross_sales per affiliate.
2. POST again with from: now-14d, to: now-7d to get the prior-week baseline.
3. For each affiliate with time_created < today - min_tenure_d:
- rank by chosen metric this week
- compute WoW delta vs prior week
- label "spike, not trend" if affiliate is in this-week top_n but not in 14-day top_n
4. Build a clean ranked digest of the top_n with:
- rank, affiliate name, this-week metric value, WoW delta, label
5. List affiliates with time_created >= today - min_tenure_d under a separate
"New this period" section so newcomers are visible but don't pollute the main board.
6. Send via the configured channel (Slack webhook + email).
# role
You are an Everflow reporting assistant. Answer conversationally first, then deliver the structured digest below.
# inputs
api_key = {API_KEY}
network_id = {NETWORK_ID}
top_n = {TOP_N} # default 10
metric = {METRIC} # gross_sales | payout | total_conversions
window_days = 7
min_tenure_d = 30
email_to = {EMAIL_TO}
slack_webhook = {SLACK_WEBHOOK_URL} # optional
# task
Pull this-week and prior-week numbers from /v1/networks/reporting/entity (columns: ["affiliate"]).
Exclude affiliates with time_created within the last min_tenure_d days from the main board, and surface them in a separate "New this period" block at the bottom.
Compute WoW deltas. Anyone in this-week top_n but missing from the 14-day top_n gets a "spike, not trend" label.
# output
Open with one sentence on what changed. Then the ranked top_n digest. Then the "New this period" block. Then send via Slack and email if configured.
# role
You are an Everflow reporting assistant. Return the digest as a markdown table.
# inputs
api_key = {API_KEY}
network_id = {NETWORK_ID}
top_n = {TOP_N} # default 10
metric = {METRIC} # gross_sales | payout | total_conversions
window_days = 7
min_tenure_d = 30
email_to = {EMAIL_TO}
slack_webhook = {SLACK_WEBHOOK_URL} # optional
# task
1. Pull /v1/networks/reporting/entity for the last 7 days and the prior 7 days.
2. Exclude affiliates younger than min_tenure_d from the main ranking.
3. Build a markdown table: | Rank | Affiliate | This week | WoW Δ | Label |
4. Tag any "this-week top_n, 14-day not-top_n" rows as "spike, not trend".
5. Below the table, list "New this period" affiliates separately.
6. If a slack_webhook is set, POST the table as Slack markdown. If email_to is set, send the same.
# Same logic, scripted with curl + jq for ops teams that prefer a shell pipeline.
# Replace {API_KEY}, {NETWORK_ID}, {TOP_N}, {METRIC} before running.
NOW=$(date -u -d '0 seconds' +%s)
SEVEN_DAYS_AGO=$(date -u -d '7 days ago' +%s)
FOURTEEN_DAYS_AGO=$(date -u -d '14 days ago' +%s)
curl -s -X POST https://api.eflow.team/v1/networks/reporting/entity \
-H "X-Eflow-API-Key: {API_KEY}" \
-H "Content-Type: application/json" \
-d "{\"from\": $SEVEN_DAYS_AGO, \"to\": $NOW, \"columns\": [\"affiliate\"]}" \
| jq '.table | sort_by(.payout) | reverse | .[0:{TOP_N}]'
# Min-tenure exclusion + WoW delta + "spike, not trend" labeling
# is most readable as a follow-on Python pass — pipe the JSON above into a 30-line script
# (template in the recipe repo).
Generate an API key in Core Platform
Core Platform → Control Center → Security → API Keys → click the + API key button. Read-only on Reporting is enough.
Pick where the digest should land
Grab a Slack incoming webhook URL for the channel where the digest should land (e.g. #weekly-digest). That's what the prompt below sends to.
Paste your keys into the prompt
Replace {API_KEY}, {NETWORK_ID}, {TOP_N} (default 10), {METRIC} (default gross_sales), and {SLACK_WEBHOOK_URL} in the prompt block below.
Run it in Claude, ChatGPT, or Gemini
The first run gives you last week's top N as a Slack message. Verify the numbers match what you'd see in Reporting.
Optional — schedule it for Monday 8am
Drop the prompt into Make, Zapier, or Google Apps Script. Set a weekly trigger. Done — the digest lands every Monday before standup.
The recipe sums revenue across the whole window, so a one-day spike will rank a partner higher than a steadier earner. Add a daily_breakdown column to the prompt if you want median-day-revenue alongside total. For most weekly digests the total is the right number — it's what gets paid out.
That's a feature for some networks and a bug for others. Add an advertiser_id filter to the prompt to get "top per advertiser" digests. Agency operators running multi-advertiser networks usually want one digest per managed brand.
Refunds typically post after the original window closes, so last week's top N may shift slightly when you re-pull a month later. For finance reconciliation, rerun with a wider window (30 or 90 days). For weekly stakeholder updates, last-week revenue is the right snapshot. For chargebacks specifically, the reversal postback flow keeps your data clean when they fire.
If an affiliate joined in the last 30 days, the prompt skips them in the main top-N list and lists them separately under "New this period." Otherwise a brand-new partner's first $1k week can look like a meteoric rise that isn't actually a rise.
The two-window confirmation (last 7d AND last 14d) protects against one-week spikes getting misread as trends. If an affiliate is top-5 over 7d but not over 14d, they're labeled "spike, not trend."
If you run a manual scrub on conversions (holding a percentage as on-hold conversions for later review), released conversions can backdate into last week after the digest already fired. Rerun the prompt with the same window after a major release. The top-N can shuffle by a position or two.
Chargebacks and refunds for subscription or high-ticket offers can post weeks after the original conversion and won't appear in a 7-day rerank. If finance pulls the same week later for a board number, expect the top-N list to shift. Best practice: rerun the prompt with a 30-day window once a month and compare.
Most accounts have a Test Partner (commonly Partner ID 1) that gets used for live QA and integration checks. Excluding affiliate_id=1 plus any partner names matching "test" / "internal" / "QA" in the prompt keeps your top-N list clean. Worth a one-time audit of your test-partner IDs before the cron starts firing.
Drop us the question you wish had a prompt. We'll write it, test it against real Everflow data, and ship it as the next recipe — usually within two weeks.
One Tuesday email. Latest industry news plus new recipes the day they ship. Unsubscribe in one click.
Share what's working with the Everflow API. Our team will reach out about details, timelines, and next steps.
