For more information on finding a record ID check out our support documentation here. Static record ID - A record ID string will be typed or copy/pasted into the field, so that the same corresponding record ID will be updated each time the button you configure in the next step is clicked in Slack.Then, you can either statically or dynamically configure which record to update.Click the dropdown menu under Table and choose a table from the base. First, you'll choose a table in the base where the record resides.Next, you'll need to configure how the automation will define which record will be updated when a Slack user presses a button in the Slack message. By default, messages sent from an Airtable automation will appear as from Airtable with an Airtable logo, so this step is optional. If you are using the Slack: Send a message action, then you can configure the way the bot will appear in Slack. In fact, for our example, we might want to include a link to the specific Airtable record so that an approver can quickly navigate to the record to get more details before they approve the project. It's worth noting that you can also Slack users or insert hyperlinks into the message. Here's what that could look like in Airtable from the automation's configuration window:Īnd here is how that would appear in Slack: We'll start the message with some text, add a record list token that will include only the most vital field information from Airtable, and then finish with some helper text about the button we will configure in a few steps. In our example, we want to use a mix of static and dynamic information to format the message. More information about Markdown usage in Slack is available here. Speaking of formatting, you can also utilize Markdown to format the way that the message will appear in Slack. You'll likely find that mixing both static and dynamic information is the best for formatting your message in a succinct and informative way. Entirely dynamic (insert as tokens from information contained within fields present in previous automation steps).Regardless of your needs, it's important to know that the message can be: The message portion of the action configuration is entirely up to you and your organization's needs related to the communication or workflow that you are automating. You can find more information about dynamic messaging in another section below.ĭepending upon the Slack action type that you chose in step 2, you might approach the messaging differently. Any user in Slack can be added as a recipient but only users with base/workspace access at the Editor permission level or higher can interact with buttons in the message.If you choose to use the static option, then you will only be able to input a single channel name, but you can choose multiple users to include from the dropdown.Any users can be added that are associated with the Slack instance you logged in to in the previous step.If you choose to use the static option, then you will only be able to input a single channel name or user.The options differ slightly depending on which of the Slack actions you are using in your automation: You can choose to either statically send a Slack message to the same channel or user(s) every time, or you can dynamically message different channels or users for each automation run. Now you will choose where the automated message will be sent in Slack. In some use cases, you might even use multiple actions or both types of actions. However, here are a few general ideas about each action that might help you determine the correct one to use. Editors - View an automation's configuration or copy an automation's URL.Ĭreating an automation - Learn how to set up your first automation in Airtable.Ĭhoosing which Slack action to use in an automation will be very specific to your workflow.Owners/ Creators - Create, delete, duplicate, configure, or rename an automation and edit an automation's description.This article will run you through the basic setup process of an automation containing either of these actions as well as some limitations, expectations, and other details that are helpful to know. When the automation runs successfully, a corresponding Slack message will be sent to the specified Slack channel, or user(s), containing the message you customized during the automation configuration process. When building an Automation, you may choose between the Slack: Send a message or Slack: Send an actionable message actions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |