Triggers

How a rule works

A rule reads as one sentence: when this happens, publish this template to these accounts. When the rule fires, PostRite creates a normal post and sends it through the same publishing pipeline as anything you schedule. Retries, failure notifications and analytics work the same way.

Enlarge

Connect a channel

A rule listens to an external account. Today that means a Twitch channel, connected from Triggers in the sidebar. The channel is a trigger source, not a publishing destination: Twitch never appears as a place to post, and it does not count toward your plan's connected accounts.

1. Open Triggers and click Connect on the Twitch card.
2. Authorize PostRite in the window that opens. We only ask for enough access to confirm the channel is yours.
3. The channel appears with a Listening badge once Twitch confirms the connection.

If the badge ever reads "Not listening", the connection to Twitch broke on their side. PostRite repairs it automatically once a day, and you can reconnect the channel at any time to fix it immediately.

Create a rule

1. Choose the channel and the trigger: when you go live, or when your stream ends.
2. Pick the template to publish.
3. Select the connected accounts it should publish to.
4. Optionally narrow it with conditions, and set the guardrails below.
5. Save. The rule is live as soon as it is switched on.

Options some platforms need

A few destinations need a setting that belongs to one specific account. The rule asks for those once and applies them to every run. Everything else about what gets published comes from the template.

• Discord: pick the channel. If you connected the server through a webhook, the webhook already points at one.
• Pinterest: pick the board.
• WhatsApp: enter the recipient number.
• TikTok: pick who can see the post.
• Everything else lives on the template: the text (including different text per network), the media, the YouTube title, the Google Business event or offer, and the rest of the network options.
• Instagram, TikTok and Pinterest only publish with media, and YouTube only with a video, so the template has to include it.

The rule is checked when you save it, so anything missing is flagged in the form instead of turning into a failed run later. The message names the network and the reason. The check runs when you change what the rule publishes or when you switch it on. Turning a rule off always works, even while it has a problem, because that is how you stop it. The form also shows the chosen template's content and media, so you can see what the rule will post.

Using live stream details in the post

Your template can use details from the stream that triggered it. Write a variable anywhere in the template and it is replaced when the post goes out:

• {{stream_title}}: the title of the stream
• {{stream_game}}: the category the channel is set to
• {{stream_started_at}}: when the stream went live, in your workspace timezone. It only exists on the When I go live on Twitch trigger. A rule that reacts to a stream ending does not offer it.
• {{channel_name}} and {{channel_login}}: the channel's display name and handle
• {{channel_url}}: the public link to the channel

Firing only for some streams

Conditions let one channel drive different posts. Leave them empty and the rule fires for every stream.

• Only these categories: the rule fires only when the channel is set to one of the categories you list.
• Only when the title contains: the rule fires only when the stream title includes a word you choose.

Guardrails

Three settings keep a rule from posting more than you want:

• Cooldown (minutes): the minimum time between two posts from the same rule. The default is six hours.
• Max runs per day: a hard limit, counted in your workspace timezone.
• Delay (seconds): how long to wait after the event before publishing.

Seeing what happened

Every rule keeps a history. It records the runs where the rule did nothing on purpose as well as the runs where it published. If you want to know why a post did not go out, look here:

• Published: a post was created. Open it to see how it went out.
• Skipped: shown with the reason. The run was inside the cooldown, the daily limit was reached, the conditions did not match, no connected account was left to publish to, the template was deleted, or the subscription is inactive.
• Failed: the rule matched but the post could not be created.
• Runs are kept for 90 days and then deleted, so the history covers recent weeks, not the last quarter.

Testing a rule

The Test button fires the rule immediately with example stream details. It ignores the cooldown and the daily limit, and nothing else. Your conditions are still evaluated, so a rule that filters on a game the example does not match records a skip instead of posting. A lapsed subscription also skips it. The test publishes for real, so you see what your audience would see. Check the result in the history and delete the post if it was only a test. A test that errors is written to the history as a failure, with the reason.

Good to know

• A workspace has a limit on how many rules it can hold, far above what any plan's posting allowance would use. PostRite tells you the number if you reach it.
• Automated posts never wait for approval. The event they react to is over long before an approver could answer.
• Automated posts count toward your monthly post allowance like any other post.
• Disconnecting a channel turns off the rules that used it but keeps them, so you can point them at a channel again later.