Turn new Peerbound stories into a weekday marketing kit

Each weekday morning, repurpose newly approved Peerbound customer stories into LinkedIn copy, sales email blurbs, and one-pager bullets, then ping marketing in Slack.

Agentic Task
PeerboundGoogle DocsSlackMarketingSalesContent GenerationDaily Digests

Every weekday at 9am Eastern, find newly approved Peerbound customer stories from the last 24 hours and turn each one into a ready-to-publish marketing amplification kit, then ping the marketing team in Slack.

Trigger: cron, Monday through Friday at 9am ET.

Step 1. Call Peerbound List Stories with updated_since set to 24 hours before the run time. Filter the results to stories that are approved for public use and exclude soft-deleted records. If the filtered list is empty, exit the run quietly without posting to Slack.

Step 2. For each qualifying story, do the following:

a) Call Google Docs Create Document with a title like "{Customer Name} — Amplification Kit".

b) Call Google Docs Batch Update Document to populate the doc with three sections drafted from the Peerbound story content, quotes, and use-case metadata:

• LinkedIn post: a scroll-stopping hook, a short narrative summary, and a verbatim pull quote from the customer.

• Sales email blurb: one tight paragraph an AE can paste into an outbound email, leading with the customer's outcome.

• Sales one-pager bullets: the strongest proof points, named metrics, and outcomes as a clean bullet list for decks.

Step 3. Once all docs are created, call Slack Send a Message to #marketing-content with a single summary message that lists each new story by customer name, includes the headline customer quote, and links directly to the corresponding Google Doc. Use Slack mrkdwn formatting.

Notes: keep the drafts persona-tuned for each surface (LinkedIn = punchy and social, email = direct and outcome-led, one-pager = factual and bullet-driven). Use the customer name, embedded quotes, and use-case metadata that come back on each Peerbound story rather than inventing details. Never post to Slack on a zero-story day.

Additional information

What does this prompt do?
  • Wakes up every weekday at 9am and checks Peerbound for customer stories approved for public use in the last 24 hours.
  • For each new story, creates a Google Doc with three ready-to-use drafts: a LinkedIn post with hook and pull quote, a sales email paragraph an AE can paste into outbound, and a sales one-pager bullet list of the strongest proof points.
  • Posts a tidy summary in your marketing Slack channel with the customer name, the headline quote, and a link straight to the doc.
  • Skips the run silently on days with no new stories so the channel only lights up when there is real news to share.
What do I need to use this?
  • A Peerbound account with API access enabled. You need an organization admin to create the key.
  • A Google account that can create Google Docs in the right shared folder.
  • A Slack workspace and a channel for marketing announcements, like #marketing-content.
How can I customize it?
  • Change the timing. Run it once on Monday morning, twice a day, or only after a launch window.
  • Swap the Slack channel, or send tailored summaries to multiple teams (a sales-flavored version to #sales, a brand-flavored version to #marketing-content).
  • Tune the three drafts. Add a press release section, drop the one-pager, or pin the LinkedIn voice to a specific exec's style.

Frequently asked questions

What happens on a day with no new stories?
Nothing. The workflow exits quietly without posting to Slack so your marketing channel only fires when there is a fresh story to share.
Can I post to more than one Slack channel?
Yes. You can add extra channels, or generate a tailored summary per audience, for example a sales-flavored version in #sales and a brand-flavored version in #marketing-content.
Where do the drafts come from?
Geni reads the approved story content from Peerbound, including the customer name, customer quotes, and use-case context, then writes copy tuned for each surface.
Can I change which stories qualify?
Yes. By default it pulls stories approved for public use in the last 24 hours, but you can filter by industry, use case, or tag.
Do I need to be a Peerbound admin to use this?
Only to create the initial API key. Once Peerbound is connected, the workflow runs on its own.

Stop letting fresh customer wins sit unused.

Connect Peerbound, Google Docs, and Slack once, and Geni turns every approved story into shareable copy by 9am.