Most teams don’t struggle with what to post.
They struggle with the annoying glue work:
You publish a blog post → you copy the link into Slack → you open your scheduler → you paste the title → you format 5 platform versions → you upload images again → you forget to post it on X → it’s Friday → you hate your life.
FeedHive Triggers exist to delete that entire checklist.
A Trigger is a URL you can call to make FeedHive do something.
Think: a webhook endpoint that creates/publishes social posts.
In FeedHive, a trigger can be configured to:
Under the hood, you’ll usually trigger it via POST with JSON (recommended). GET still exists for legacy setups.
If you remember just one thing, make it this:
Your other tools detect events. FeedHive ships posts. Triggers connect the two.
Once you have a Trigger, anything that can send a webhook can create/publish social content.
I’ll keep these practical. Each workflow below is something you can build in 15–30 minutes.
Use when: you want consistent promos for every article without rewriting the structure every time.
How it works:
[[title-of-blogpost]][[excerpt-of-blogpost]][[link-to-blogpost]]Result: a draft appears in FeedHive with the right structure, ready for approval.
Use when: you want one “source” event to generate multiple posts (LinkedIn, X, Instagram, etc.) but still review them.
How it works:
Result: three drafts, each already formatted for the platform.
Use when: you publish videos and want instant distribution.
How it works:
title (platform-specific variable)link (platform-specific variable)text (caption)Result: your video promotion is ready the minute YouTube is live.
Use when: you want more than one “we have a new episode” post.
How it works:
text or different template variablesscheduled timesResult: a full mini-campaign, not a single post.
Use when: you want to celebrate wins without accidentally leaking customer info.
How it works:
Result: you get the draft when the moment is fresh, but you still control what goes public.
Use when: testimonials show up randomly and get lost.
How it works:
[[quote]], [[name]], [[role]], [[company]], [[link]]Result: every testimonial becomes a post candidate (and you stop wasting good quotes).
Use when: you want hiring to be a one-click workflow.
How it works:
text, link, and optionally media_urlsResult: instant distribution, zero coordination overhead.
Use when: you ship often and marketing can’t keep up.
How it works:
[[version]], [[highlights]], [[link]]Result: marketing gets a ready-to-edit draft for every release.
Use when: you want automation to generate first drafts, but still keep your voice.
How it works:
text, you send a promptExample prompt idea:
“Write a short LinkedIn post announcing our new blog article. Keep it punchy, no corporate fluff. Include 1 hook, 2 key takeaways, and a soft CTA. Use this info: title={{title}}, excerpt={{excerpt}}, link={{link}}.”
Result: your workflow creates drafts that don’t start from a blank page.
FeedHive triggers support:
curl -X POST https://api.feedhive.com/triggers/xxxxx \
-d '{
"text": "Your post content here",
"scheduled": "2024-01-15T10:00:00Z",
"media_urls": ["https://example.com/image1.jpg", "https://example.com/image2.jpg"]
}'
A few practical notes:
text is required unless a template is assigned to the trigger that provides the post content.scheduled is only used with “Create & Publish”.media_urls is the easiest way to attach images/videos from other systems.In your template, you can use custom variables like [[link-to-blogpost]].
When triggering, send them as JSON fields in the POST body. FeedHive will replace them at runtime.
Start here:
If you want automation in the other direction (FeedHive → your tools), that’s what Notifications are for: FeedHive can call a webhook when something happens (like a post going live).
If you want the step-by-step setup, start here:
Once you set up your first Trigger, you’ll never want to go back to copy/paste workflows again.