Post Updates to Multiple Channels
Automatically post to your preferred internal channels when you publish new content to Workplace
Keep your staff engaged by posting announcements to their favourite channels when you add new content to the intranet, or even making a calendar booking for all-hands meetings.
By using meta data you can automate this process, while retaining control over what gets posted, as well as where and when.
This recipe includes two flows, one for Microsoft Team & Outlook and the other for Slack, but you can easily limit the accounts you want to post to by deleting the flow that the solution doesn't require.
It’s easy to integrate using a Recipe. All you need is the right credentials to connect. We recommend you test the integration with a Sandbox account before using it in production.
- Click the Activate recipe button to deploy this Recipe in Squiz Connect.
- Sign into Squiz Connect if you’re not already signed in.
- Follow the on screen instructions to finish deploying the Recipe.
Activating the recipe
The following simple configuration steps need to be carried our as part of the recipe activation. Greater details for steps 2-4 can be found below.
- Delete any flows you do not need (e.g. you may use the Slack flow but not the Teams flow)
- Configure Slack / Teams to get the required webhook urls
- Finish Activating the recipe in Connect
- Set up Slack / Teams / Outlook to display the posts in your chosen format
Getting the webhook url from MS Teams
- Configure an incoming webhook connector in the relevant channels - for example your News channel and your Announcements channel using the instructions available at this link.
- Copy the webhook url.
- Format your JSON string using the example below by pasting the webhook urls into the space provided:
- Paste the JSON into Connect as in Step 3 of the Recipe Activation process
{
"announcement_url":"<REPLACE THIS VALUE WITH THE TEAM WEBHOOK CONNECTOR URL>",
"news_url":"<REPLACE THIS VALUE WITH THE TEAM WEBHOOK CONNECTOR URL>"
}
Manage how your messages display in Slack
The recipe provides you a default message card template. The default message card looks like this:
You can update the format of the message card by editing the Post announcement to Team and Post news to Team steps of the Workplace Content Social Distribution (Team & Outlook) flow.
Click on Edit flow to create a draft flow of Workplace Content Social Distribution (Team & Outlook). The message card format source code can be located at the Body field at the Input tab for the following steps.
Manage how your Outlook events displays
The recipe provides you a default calendar event template. The default event looks like this:
You can update the event detail by editing the Create event in Calendar step of the Workplace Content Social Distribution (Team & Outlook) flow.
The source code of the Outlook event can be located at the configuration tab.
Getting the webhook URL for Slack
- Configure an incoming webhook connector in the relevant channels - for example your News channel and your Announcements channel using the instructions available at this link.
- Copy the webhook url
- Format your JSON string using the example below by pasting the webhook urls into the space provided:
- Paste the JSON into Connect as in Step 3 of the Recipe Activation process
{
"announcement_url":"<REPLACE THIS VALUE WITH THE SLACK WEBHOOK URL>",
"news_url":"<REPLACE THIS VALUE WITH THE SLACK WEBHOOK URL>"
}
Manage how Slack displays you messages
The recipe provides you a default Slack message template. The default message looks like this:
You can update the format of the message card, select the slack channel for sending the message by editing the Post announcement to Slack and Post news to Slack steps of the Workplace Content Social Distribution (Slack) flow.
Click on Edit flow to create a draft flow of Workplace Content Social Distribution (Slack). The message format source code can be located at the Body field at the Input tab for the following steps.
Type | Recipe |
---|---|
For | Integrations (Connect) |
Flows | 2 |
Documentation |