Weekly Tasty trends digest for content teams (Slack)

Every Monday at 9am New York time, run a weekly "what's trending on Tasty this week" digest and post it into our content team's Slack channel so our food writers and social team start the week with a shortlist of riffable recipes.

Step 1: pull the feed. Call Tasty's List Feeds operation with our timezone in +hhmm format (for example -0500 for New York). That returns the latest homepage feed items, which is the trending mix we want to riff on.

Step 2: editorial pick. Use your judgement to pick the three or four most distinctive recipes from that feed. Vary cuisine across the picks, skip anything that looks like a near-duplicate of last week's picks, and favour recipes with strong visual potential (great hero photo, eye-catching colour, clear hook). Do not just take the top three off the top of the feed.

Step 3: optional remix angle. For each pick, optionally call Tasty's List Similar Recipes operation if seeing nearby recipes helps you suggest a sharper "remix angle" the content team could write about. Skip this call for picks where the angle is already obvious.

Step 4: post the digest. Use the Slack Bot Send a Message operation to post a single nicely-formatted message into our content team's Slack channel. For each recipe include the title, the image, the prep time, the Tasty link, and a one-line content-angle suggestion such as "summer twist on a comfort classic" or "5-ingredient TikTok hook". Use Slack's mrkdwn formatting and keep everything in one message (not a thread). Keep the layout tight enough that the whole digest reads in under 30 seconds.

Make the Slack channel, the timezone, the number of picks, and the editorial brief easy to edit later so the marketing lead can tune it without rebuilding the workflow.

Additional information

What does this prompt do?

Pulls this week's featured items from Tasty's homepage feed every Monday morning.
Picks the three or four most distinctive recipes, varying cuisine and skipping near-duplicates of last week's picks.
Suggests a one-line content angle for each recipe so writers have a starting hook (a summer twist, a 5-ingredient TikTok riff, a comfort-food remix).
Posts a single tight Slack message your food writers and social team can scan in under 30 seconds.

What do I need to use this?

A Tasty API key from RapidAPI. The free Basic plan covers a weekly run with room to spare.
A Slack workspace with a channel where your content team hangs out, with the Geni bot added to it.
The timezone you want the feed pulled in (for example New York or London) so the trending list matches your audience.

How can I customize it?

Change the day or time it runs. Fridays at noon for a weekend planning shot, or Sunday night before the week begins.
Swap the destination. Point it at a private content-team channel, a marketing brainstorm room, or even a DM to the editor.
Tune the editorial brief. Ask for more picks, fewer picks, only quick weeknight meals, only desserts, or only recipes with bold visual potential.

Frequently asked questions

Where do the trending recipes come from?

Tasty's own homepage feed, pulled live each Monday morning through the public Tasty API on RapidAPI. It is the same feed Tasty surfaces to its readers, so it tracks what is actually getting traction this week.

Will it keep recommending the same recipes week after week?

No. The agent is briefed to vary cuisine across the picks and skip anything that looks like a near-duplicate of last week's shortlist, so each Monday's digest feels fresh.

Do I need a paid Tasty or RapidAPI plan?

The free RapidAPI Basic tier (500 requests per month) is plenty for one weekly run. Heavier use is fine too, just upgrade the plan when you outgrow Basic.

Can I change the editorial style of the picks?

Yes. The brief inside the workflow is plain English. Tell it to favour seasonal recipes, viral TikTok-style hooks, vegetarian-only, dessert-only, or whatever angle your audience cares about.

Does this post as a bot or as me?

It posts as the Geni Slack bot, so the digest stays on a clean automated cadence even if the person who set it up leaves the company.