Skip to content

Publishing to your own channels

Learn it in the academy: Publish to your own channels (video)

Social connections need Org plan. Connecting and posting is limited to people holding the social connection permission — in practice an organisation’s administrators and owner.

An organisation can connect its own accounts and post to them without leaving the platform. That is different from a reader sharing a public page: see Your project in public for that. Here the post goes out from your organisation’s own account, under its own name.

Nine channels can be connected. They fall into two kinds, and the kind decides what you are asked for when you post.

Broadcast — a short post with an image. Bluesky, LinkedIn, Mastodon, Facebook and Instagram. You write a caption and attach an image.

Article — a full post on your own website. WordPress, Ghost, Webflow and Wix. You give a title and a body written as rich text, choose whether it is a draft or is published straight away, and add a featured image. The post is created in your site’s own content system, so it appears wherever your site shows its posts.

Open Settings → Integrations and choose the Social tab. Each channel is a card with a Connect button. A card that is greyed out is one the platform has not switched on, and cannot be connected.

The Social tab: the channels an organisation can connect and post toOpen /a/settings/integrations in the app
The Social tab: the channels an organisation can connect and post toThe Social tab: the channels an organisation can connect and post to
https://actionnetwork.world/a/settings/integrations

How you connect depends on the channel.

Sign in with the network — Facebook, Instagram, LinkedIn and Mastodon. A window opens on the network’s own sign-in and asks you to approve access. Mastodon first asks for your instance (the server your account lives on), because there is no single Mastodon to sign in to.

Paste credentials — Bluesky, WordPress, Ghost, Webflow and Wix. There is no sign-in window; you supply what the service needs to accept posts on your behalf:

Channel You supply
Bluesky Your handle or email, and an app password — not your account password
WordPress The site URL, a username, and an application password
Ghost The site URL and an Admin API key
Webflow A site API token, the CMS collection ID to post into, and the body field slug the article text should go in
Wix An API key, the site ID, and a member ID to post as

Bluesky and WordPress ask for an app or application password rather than your normal one. Create it in the service’s own settings, so it can be revoked without touching your real login.

Once a channel is connected, its card offers a post action. The form shows only the fields that channel accepts.

Fields
Bluesky, LinkedIn, Mastodon Caption, and an image if you want one
Facebook, Instagram Caption and an image — the image is required
WordPress, Ghost, Webflow Title, body, status (draft or publish), featured image
Wix Title, body and status — no featured image

Draft means draft. On the four article channels, choosing draft creates an unpublished item in your site’s system for you to review there; choosing publish makes it live. Webflow publishes to the live site directly when you choose publish, and Wix creates the post and then publishes it.

An image that does not suit the channel is a rejection you would rather learn about early. The form tells you the rules for the channel before you submit.

Instagram is the strict one. It accepts JPEG only, and the picture must sit between a 4:5 portrait and a 1.91:1 landscape shape. An image outside that window is refused. For an image the platform hosts, it prepares a conforming copy for you.

Facebook and Instagram will not post without an image. A text-only update cannot go to either. An update with a video can: Facebook gets the video’s link, Instagram a Reel.

Facebook posting goes to a Page your account manages, not to a personal profile. If your account manages several, choose which one under Posts to on the Facebook card in Settings → Integrations — until a Page is chosen, nothing is posted, and the card says so. With one Page, that Page is used. Reconnecting the same account keeps your choice. If your account manages no Page, posting fails with a message saying so.

A connected channel can also receive your project updates by itself: when an update is published, the platform shares it to every channel an administrator has switched on, so nobody has to post it again by hand.

Switching a channel on. On each connected card in Settings → Integrations, choose how the channel takes part:

Setting What happens when an update is published
Off Nothing. You can still post to it by hand
Yes — publishers can untick it It is shared, unless the person publishing leaves it out
Always It is always shared. Publishers do not see it in the list

Webhooks that receive update published take part the same way: they are always sent by default, and a row action makes one optional.

Three channels are handled differently. LinkedIn cannot be switched on — it posts as the person who connected it, not as the organisation, and posting to a company page is not available yet. Bluesky and Mastodon ask you to confirm that the account is your organisation’s own before they can be switched on, because the platform cannot tell an organisation’s account from a person’s.

What the person publishing sees. When an update is public and there are optional channels, publishing has a second step: the update’s title, and the channels it will go to, each ticked. Untick any you want to leave out, or write different text for one channel — a shorter version for Bluesky, say. The mobile app works the same way, and an update published with no signal is shared once the phone is back online.

Before anything leaves. Every share waits a few minutes (five by default) so a mistake can be undone from the update itself. In that time a light automated check looks at the photos and text for pictures that would not work and for inappropriate content — it does not judge people, consent or anything else. What happens next is the organisation’s review policy, under Settings → Integrations → Sharing:

Review policy
Off Shared after the undo window
When the check flags something (the default) Flagged posts wait for an administrator
Always Every post waits for an administrator

A post that waits appears in the Sharing tab, where an administrator can approve it — editing the text per channel first — or decline it with a note for the person who published. A waiting post sends the administrators a reminder after a day and is declined automatically after a week. If the check cannot run at all, the post is treated as flagged — under the default policy it waits.

Where it went. Each update shows its sharing status per channel: sent, waiting, failed, or needs reconnecting. A temporary failure is retried by itself; a channel whose sign-in has expired is marked for reconnecting, and one that fails five times in a row is paused until an administrator turns it back on. If the platform cannot tell whether a post went out, it says so rather than posting twice — mark it as posted, or retry.

  • Anything that is not public. Only a public update, in a public project, ever leaves the platform — webhooks included. Making the project private stops shares that have not gone yet.
  • Video. A video is shared with the update: as a link where the network plays it, as a Reel on Instagram. Project updates says how each network gets it.
  • Edits. An update is shared once, when it is first published. Changing it afterwards does not change the posts, and unpublishing or deleting it does not delete them — remove a post on the network itself. Share again on the update posts it once more, on purpose, to the channels you choose.

Networks change what they ask for, and a connection made under the old terms can lose the right to post. When that happens the card shows a reconnect notice — permissions have changed, so posting may fail — instead of a green tick. Posting is not blocked, it is warned about: reconnect and the notice clears.

Disconnecting a channel removes the platform’s access and switches automatic sharing off for it. You can reconnect it later — sharing then stays off until an administrator switches it on again.

A post sent by hand is not tied to an update. Posting from a card sends the caption and image you give it. It does not publish, link to or take anything from a project update. To send an update itself, publish the update and let automatic sharing carry it.

A public update can be passed on without any of this. A reader can share it to LinkedIn, Facebook, X, Bluesky or Mastodon from its page, and X is available there though it is not something you can connect here. See Your project in public.

Something wrong on this page? Report it