Automation · Content and publishing
Publish to Instagram and Facebook the moment somebody approves the piece
How an AI agent publishes to Instagram and Facebook as soon as the piece is approved on the content board, generating the image when it is missing.
How do I publish to Instagram and Facebook without scheduling every piece by hand?
The team works content on a board inside Meteor. When somebody moves a record to approved, the task fires: the Met generates or adjusts the image if it is missing, checks how much publishing quota is left in Instagram's rolling 24 hour window, publishes in the right format (image, carousel, reel or story) and mirrors the message on the Facebook page. Approval stays human. What disappears is the work of copying, uploading and waiting.
What starts it
When a record changes state
A task that listens for a field on the content record moving to a specific value: the status changing to Approved, for example. It is the right trigger for a kanban style board and it is enabled in the product, unlike others that sound obvious and are not.
A task that listens for a record being created, or for one of its fields moving to a specific value such as "Approved".
Who runs it
Met for content
Social team
It has no seeded name in the product: it is an internal marketing Met. Its work starts once a person has decided the piece goes out, and ends when the piece is published.
What you need connected
- Facebook and Instagram Content and websites
- Replicate Content and websites
5 steps · 11 tools
The procedure, step by step
Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.
- 1
Know which account publishes, and how much quota is left
The account listing returns the connected Facebook and Instagram pages with their identifiers; with more than one brand, picking wrong means publishing on the wrong profile. The publishing limit says how many posts are left in Instagram's rolling 24 hour window (a carousel counts as one) and is what keeps a batch from stopping halfway.
- 2
Generate or adjust the piece
If the record already carries the image, this step is skipped. If not, generation produces the piece from the text on the record, and editing adjusts an existing one: change the background, clean up an element, adapt the format. The model listing lets you pick the one that fits the brand style instead of always using the same one out of habit.
- 3
Publish an image or a carousel on Instagram
Publishing an image handles internally the two step flow Meta requires, and a carousel takes from two to ten pieces mixing images and video. One thing to be clear about: the source has to be a public URL. A file that only exists on somebody's computer cannot be published.
- 4
Reels and stories, with their processing time
Reels do not publish instantly: Meta processes the video and the tool waits until it finishes before publishing. Stories vanish after 24 hours, so they work best as reinforcement for a feed piece and not as the main content. The video can also be generated first, when the record does not carry one.
- 5
Mirror the message on Facebook
A Facebook page accepts text only, text with a link, or a photo with a caption. That is not the same as Instagram and it should not be: on Facebook the link works, and publishing the same text without using it wastes the one format on that network that sends traffic to your site.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
A Facebook page and a professional Instagram account, connected
You authorize them from Meteor with the account that administers the page. The Instagram account has to be professional and linked to a Facebook page: that is a Meta requirement.
-
A Replicate credential
A token from your Replicate account. You only need it if you are going to generate or edit pieces; if your team already brings the artwork, that step is unnecessary.
-
A content board with an approval status
You build it as a collection in Meteor, with whichever status field you want. The trigger listens to that field, so you decide what the status is called.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not schedule future posts inside Meta. It publishes when it is triggered; if you want a fixed hour, the thing you schedule is the task.
-
It does not reply to comments or direct messages. Publishing and conversing are two different jobs, with different connectors.
-
It does not measure how the post performed. It brings no reach, engagement or follower data: that is what the Meta panel is for.
-
It does not decide what to publish. Approval is human on purpose: the trigger exists precisely so that nothing goes out until a person has moved it to approved.
FAQ
Questions about this automation
Because Instagram caps posts per account inside a rolling 24 hour window. In a large batch, running out of quota halfway leaves half the content published and half of it not, with no visible reason from the outside.
Not directly: Meta requires a public URL to publish. The image has to be uploaded somewhere reachable. Whatever the image connector generates already is.
The tool returns Meta's error and the task stops there. The case stays visible for somebody to review, instead of retrying in a loop against a platform restriction.
Keep going
Other automations built on the same tools
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.