Skip to main content

Posted by platform connector

A channel with Handed over by platform connector switched on in its Settings (Channels) is posted by Reelwire itself. When a post is due, Reelwire puts the video and its text on the channel's platform, with the credentials saved in that section of the channel's Settings, and marks the post Published with its link. Nobody opens an email and no system of yours receives a webhook for it, unless you switch those on as well.

Each platform decides who may post through it. Discord, Slack and Telegram let your own bot, webhook or app post, so their connectors ask for what you make there. Facebook, Instagram, LinkedIn, Pinterest, Threads, TikTok, X and YouTube let an app post for other people only once they have reviewed it, so Reelwire posts there through Zernio, a posting service whose app they approved: you connect your account with a button named for the platform, such as Connect TikTok account, by signing in on the platform itself, and type nothing. That is part of the Individual plan and above, each of which includes a number of connected accounts: one on Individual and as many on Business as your offer agrees (nine, unless it says otherwise). More are added on the Plan screen.

One account, several channels

Where another channel of your workspace is connected to an account on the same platform already, its Handed over by platform connector section offers Use an account connected already, a dropdown above the connect button. Choose that account and press Save, and this channel posts there too, with no new sign-in. An account counts once against your connected accounts however many channels post to it, so this costs nothing more. New connection connects another account instead. The dropdown only shows where such an account exists.

Every platform​

PlatformConnectorWhat you needChangesTakes down
DiscordAvailableA webhook of the channelYesYes
FacebookThrough ZernioA Facebook Page you manageYesYes
InstagramThrough ZernioAn Instagram professional accountNoNo
LinkedInThrough Zernio, your profile or a company PageA LinkedIn account; for a Page, its administrator rightsThe textYes
PinterestThrough ZernioA Pinterest business account and a boardNoYes
SlackAvailableA Slack app of your own, invited to the channelNoYes
TelegramAvailableA bot from @BotFather, administrator of your channel or groupYesYes
ThreadsThrough ZernioA Threads profileNoYes
TikTokThrough Zernio, as a draftA TikTok accountNoNo
XThrough ZernioAn X accountNoYes
YouTubeThrough Zernio, Shorts in 9x16A YouTube channelThe descriptionYes

Changes is whether Send update request on Posts changes the text of a post the connector made; Takes down is whether Send delete request removes it, after which the post reads Deleted by itself. Where a platform does not let an app do either, the connector's mark beside the request under More is dashed, the dialogue leaves the connector out, and you do it on the platform by hand. A connector changes a post's text only: an update with a new video is refused on the post, which says to send a delete request and post it again.

A post that goes from the platform reads Deleted by itself. On the platforms you connect by signing in, a post the connector made that you delete there, or that the platform takes down, reads Deleted within a few hours. A very old post may go unnoticed; Mark as deleted under More says so at once.

Resend post request posts the video again as a new post on every platform, and on TikTok as a new draft. LinkedIn and X refuse text they already have, so there it only goes through once the text has changed.

Switch it on​

On a platform posted through Zernio there is nothing to fill in: choose the platform in the channel's dialogue, press Connect in its Handed over by platform connector section and sign in on the platform in the tab that opens. As soon as you have, the account is saved on the channel and its connector switched on. Each platform's page walks through it. On Discord, Slack and Telegram:

  1. Set up what the platform needs, as its page describes.
  2. In Channels, open the channel's Settings (or Add new channel) and choose the Platform and Aspect ratio.
  3. In the Handed over by platform connector section, press Connect. Where the workspace has credentials for the platform saved already, choose them with Use these, or press New connection.
  4. Enter what the platform gave you and press Connect. Reelwire asks the platform whether the credentials work, posting nothing, and only if they do saves them on the channel and switches its connector on, at once; the section then shows, for example, "Connected: @yourbot in Company News". When they do not work, the dialogue shows the platform's reason. Leave Handed over by email on as well if a person should still get each post, or switch it off.
  5. Where the credentials expire, set Credentials expire and switch on Email a reminder before they expire for a reminder a week and a day before, and press Save.

Saved credentials are never shown again. Disconnect takes them off the channel, and Test asks the platform again whether they still work, posting nothing. Moving the channel to another platform removes them too, when you save. Connecting and disconnecting, the expiry and the reminder need the Administration permission, as the webhook's address does, and new credentials are entered in the dashboard only: no API key or AI assistant can. Anybody else who edits channels sees whether it is connected, when the credentials expire and the last test, and can test them. Switching the connector on or off is part of the channel, like the other switches.

The channel's Posting settings, at the foot of the dialogue, go to the platform connector as they go with the email and the webhook, and the connector applies the ones its platform lets it: on Telegram, Silent post sends the post without sound and Protect content stops it being forwarded or saved. Discord and Slack have no posting settings. Through Zernio, YouTube applies Visibility and Notify subscribers, Instagram Also share to feed, Hashtags as first comment and Allow comments, and X Allow comments; each platform's page says which of its settings are applied. Mark as branded content, on Instagram and TikTok, is not applied: while it is on and the connector is too, an amber note under the switch says to set it by hand on each post.

On Facebook, Instagram and YouTube the Posting settings also say whether the account may post links, which changes the text itself rather than how it goes out. Each of those pages has a section on it.

What happens when a post is due​

  • The post goes out when it is due, like every hand-over: the channels of a post that need no approval together, a channel that needs approval on its own once approved.
  • The Connector mark on the post's row on Posts reads Posting, then Posted, and the post reads Published, with the link to it where the platform gives one.
  • A platform that asks to be called later, or that Reelwire could not connect to, is tried again after 10 seconds, a minute, five minutes, a quarter of an hour, an hour and two hours. A refusal that would come back on every try, a wrong token or a video larger than the platform takes, stops at once. Either way the post shows the platform's reason, and reads Post failed where no other way got it out; the connector's line in What went out on the Activity screen shows it too. Once you fixed it, Resend post request under More on Posts tries the post again, the ways you choose in its dialogue; Deliver again on the connector's line in What went out sends that one line once more.
  • A post is never sent twice on a guess. When Telegram, Discord or Slack had the video and then failed on its side, or did not answer, the post may be up all the same, and none of them can say whether it is. So Reelwire does not send it again by itself. The post reads Handed over, its Connector mark Failed, and its Post kit says why. Look on the platform: if the post is there, press Mark as published under More; if it is not, press Resend post request there. The platforms posted through Reelwire's posting service recognise a repeat, so those are tried again as above, and only read like this if the last try still has no answer.
  • The switch and the credentials are read when the post goes, not when it was handed over: a channel whose connector was switched off meanwhile posts nothing, and its line says so.
  • An account connected through Zernio whose connection the platform ended (its sign-in expired or was taken back) posts nothing until it is connected again: its posts fail saying so, the owners and whoever holds Administration receive one email about it, and its row on the Platform connections card says Needs reconnecting, with Reconnect, which signs it in again for every channel posting to it.
  • A post the connector already made is never posted a second time by Deliver again, which sends the same delivery once more. Resend post request on Posts, with Platform connector switched on in its dialogue, is how you post it again: a repost, a new post of the same video, while the earlier one stays where it is.

Safe keeping​

The credentials are kept encrypted and answered only masked (a secret shows its last four characters). They leave Reelwire only to the platform they are for. An account connected through Zernio is held by Zernio, which keeps the platform's sign-in and renews it: Reelwire keeps only which account it is, and never sees a password. Syndication participants never post through your connector: what they receive goes to them by email or webhook, as their group allows, and nothing about your credentials is in it. To stop a connector at once, switch it off on the channel; to end it for good, remove the saved credentials and revoke them on the platform as well.