01
Plain text
Send message text without enabling Slack markdown interpretation.
Publishing destinationFrom public post to team context
Carry every update into the Slack channel that needs it
Send social updates, useful links, and public images to Slack without adding another copy-and-paste task to your publishing routine.
Set up in minutes. Cancel anytime during your trial.
←
01
Keep teams current
Put launches and published updates in the channel where collaborators already work.
02
Preserve useful context
Deliver text, links, and public image blocks in one Slack message.
03
Use a focused destination
Connect a selected channel through a Slack incoming webhook.
How it works
Add Slack to an existing publishing workflow
Slack is destination-only. Keep creating at a supported origin, then send eligible updates to the connected channel.
- 01
Connect Slack
Choose the workspace and destination channel during Slack authorization.
- 02
Select Slack as a destination
Add Slack in a supported Ferryman publishing workflow.
- 03
Share the update
Ferryman sends the message through the channel's incoming webhook.
Platform support
What Ferryman supports with Slack
The exact behavior depends on the content, connected account, destination requirements, and Ferryman plan.
02
Link sharing
Keep article and launch URLs in the message for Slack to render.
03
Public image blocks
Show up to four publicly accessible image URLs with available alt text.
04
Video links
Videos are shared as links rather than uploaded as native Slack files.
05
Message-safe text
Keep message text within Ferryman's 4,000-character limit and image sections within Slack's 3,000-character block limit.
06
Accessible fallback text
Include top-level fallback text alongside image blocks for notifications and accessibility.
Platform details
Slack is a channel destination
- Ferryman does not read Slack messages or use Slack as an origin.
- Image blocks require publicly accessible image URLs so Slack can fetch them.
- Videos are shared as links and are not uploaded as Slack files.
- Quote posts, reposts, and native thread chains are not represented as Slack primitives.
Quick setup
Connect Slack in minutes
- 1
Connect Slack
Authorize Ferryman and select an eligible workspace channel.
- 2
Choose Slack as a destination
Add the connected channel to a supported workflow.
- 3
Publish once
Ferryman carries the eligible update into Slack.
Popular workflows
Keep exploring Slack
Slack questions, answered
Can Ferryman publish to Slack?
Yes. Ferryman can send text, links, and publicly accessible image URLs to the Slack channel selected during connection.
Can Slack be an automatic origin?
No. Slack is a destination only; Ferryman does not read channel messages as an origin.
How are images delivered?
Slack fetches publicly accessible image URLs from image blocks. Ferryman includes up to four images and preserves available alt text.
How are videos delivered?
In Ferryman's Slack destination, videos are shared as links so Slack can render the destination URL rather than receiving an uploaded video file.
Does Ferryman create Slack threads?
No. Destination posts are channel messages and do not create native Slack thread chains.
Put published updates where your team will see them
Connect a Slack channel and add it to your Ferryman destination workflow.