Message Settings

• Message type:
  
  • Send a single message sends one message with your configured text.
    
  • Send one message per row sends a separate message for each row of data.
  • Select Channel message and choose a channel, or
  • Select Direct message to user and choose a user. 
    
    • Both channel messages and DMs send from the “Parabola app”, not your own Slack profile.
    • To direct message multiple users, duplicate the Send to Slack step, filter rows for each user, and configure each step separately.
    • Direct Messages sent with this integration will appear under the “Apps” section in your Slack sidebar.
• Message text: 
  
  • Write plain text or Slack markdown.
  • Reference column values dynamically with curly braces. For example: {SKU}.
  • When sending a single message, values from the first row fill in the curly-braced references.
• Message Settings Gear icon (all on by default):
  
  • Include a link to this flow (requires appropriate flow permissions for recipients).
  • Expand URLs and images in Slack
  • Link usernames and channels. Channels can be referenced as “#general” and users as @alex
• Sending test messages:
  
  • Click Send test message to send test messages to yourself without running the full flow. Test messages do not use Parabola credits.
• Attached file:
  
  • Do not attach anything is the default message. This means that the recipient will only receive the content configured in the Message Text box and a link to the flow if you kept this enabled in your Message Settings.
  • Attach entire table as a CSV - you’ll name the CSV file that will be sent via Slack. The individual file size limit is 1 GB, based on Slack’s file upload limit.
  • Attach a file by URL - Use this setting when you have a column that contains file URLs. Merge in that column’s value by wrapping the column name in curly braces. You can also enter a file URL manually if you have one stored elsewhere.

Formatting messages with markdown 

Basics

_italic_ will produce italicized text

*bold* will produce bold text

~strike~ will produce strikethrough text

Line breaks 

You can write multi-line text by typing a new line, or insert a newline by including the string “\n” in your text.

Block quotes 

You can highlight text as a block quote by using the > character at the beginning of one or more lines.

Code blocks 

If you have text that you want to be highlighted like code, surround it with back-tick (`) characters.For example:

`This is a code block`

You can also highlight larger, multi-line code blocks by placing 3 back-ticks before and after the block. For example: 

```This is a code block\nAnd it's multi-line```

Lists 

Create lists by using a - character followed by a space. For example:

- This

- is

- a list

Links 

URLs will automatically work. Spaces in URLs will break the URL, so we recommend that you remove any spaces from your URL links.

You can also use markdown to adjust the text that appears as the link from the URL to something else: For example:

<http://www.example.com|This message *is* a link>

And create email links:

<mailto:bob@example.com|Email Bob Roberts>

Emoji 

Emoji can be included in their full-color, fully-illustrated form directly in text. Once published, Slack will then convert the emoji into their common 'colon' format. For example, a message published like this:

It's Friday 😄

will be converted into colon format:

It's Friday :smile:

If you're publishing text with emoji, you don't need to worry about converting them, just include them as-is.

The compatible emoji formats are the Unicode Unified format (used by OSX 10.7+ and iOS 6+), the Softbank format (used by iOS 5) and the Google format (used by some Android devices). These will be converted into their colon-format equivalents. The list of supported emoji are taken from https://github.com/iamcal/emoji-data.

‍

Helpful Information

• You can preview messages by sending yourself a test DM before running the Flow.
• Slack messages have a 40k character limit.
• Some Slack features (like @here) aren’t supported.
• You cannot send Slack messages to private channels.
• If you’re posting into a channel, make sure the Parabola app has been added to that channel first (or ask a Channel Manager to add it).

The Pull from Slack step is a beta step and requires more  set-up compared to our Send to Slack step.

Authentication & getting started

1. Go to the Slack App creation page.
2. Click the Create New App dropdown in the top left.
3. Select From scratch.
4. Enter Parabola for your app name.
5. Choose the workspace where you want to use the API.
6. Click Create App

Set up OAuth permissions

• In the left-hand menu, click to OAuth & Permissions

• Scroll down to “Scopes”

• Click to Add an OAuth Scope
  
  • Select the permissions your app needs. For example:
    
    • For example, if you want to read messages in a channel, select 
      
      • channels:history
      • groups:history
      • im:history
      • mpim:history

You can add multiple scopes depending on what you want the app to do.

• Next, we’re going to install the App to your workplace. 
  
  • Scroll up to “OAuth Tokens” and select Install to…‍
  • Select Allow on the next page. 

Copy the Bot User OAuth Token on the previous page. You will need it within the Parabola step as the Bearer Token

Install the app in a Slack channel

• Open the Slack channel where you want to access the data
• Click the three dots to open Channel details.

• Go to the Integrations tab
• Click to Add an App
• Search for your app’s name
• Click Add to  channel.

Authenticate & pull in data from Parabola

• In Parabola, drag a Pull from API step onto your Flow.
• Find the endpoint that you’re looking to access. 
  
  • Full List of endpoints here: https://api.slack.com/methods 
  • To easily access Channel History, you can copy and paste this into your flow: parabola:cb:cecee323-f2e9-49d2-b15e-d1f1efcf9f23 
• Slack uses the “Bearer Token” access. 
  
  • Copy and paste the Bot User OAuth Token into the token location. 
  • For the above endpoint, please ensure you also add in the Channel ID (available in the same Channel Details as where you added the app)

Helpful tips:

• The endpoint will likely have required scopes that you’ll need to ensure you include!
• For example, for Conversations History: 

‍