Slack compatibility
Origin by Corvus makes it easy to migrate integrations written for Slack to Origin by Corvus.
Translate Slack's data format to Origin by Corvus
Origin by Corvus automatically translates the data coming from Slack:
-
JSON responses written for Slack, that contain the following, are translated to Origin by Corvus markdown and rendered equivalently to Slack:
<>to denote a URL link, such as{"text": "<https://origin.com/>"}.|within a<>to define linked text, such as{"text": "Click <https://origin.com/|here> for a link."}.<userid>to trigger a mention to a user, such as{"text": "<5fb5f7iw8tfrfcwssd1xmx3j7y> this is a notification."}.<!channel>,<!here>, or<!all>to trigger a mention to a channel, such as{"text": "<!channel> this is a notification."}.
-
Both the HTTP
POSTandGETrequest bodies sent to a web service are formatted the same as Slack's. This means your Slack integration's receiving function does not need change to be compatible with Origin by Corvus.
Known Slack compatibility issues
- Using
icon_emojito override the username is not supported. - Referencing channels using
<#CHANNEL_ID>does not link to the channel. <!everyone>and<!group>are not supported.- Parameters
mrkdwn,parse, andlink_namesare not supported (Origin by Corvus always converts markdown and automatically links @mentions). - Bold formatting supplied as
*bold*is not supported (must be done as**bold**). - Slack assumes default values for some fields if they are not specified by the integration, while Origin by Corvus does not.