From 10260d319e20684ab90cb7c9e7f6a36358b6e3b9 Mon Sep 17 00:00:00 2001 From: "@zimeg" Date: Mon, 4 Nov 2024 11:43:45 -0800 Subject: [PATCH] docs: remove confusing words around providing a payload to send --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 74b6bd0..acdccb4 100644 --- a/README.md +++ b/README.md @@ -54,8 +54,8 @@ Start in Slack to create a Slack workflow: 1. [Create a Slack workflow][wfb-create] that starts from a webhook. 2. Copy the webhook URL and [add it as a repository secret][repo-secret] called `SLACK_WEBHOOK_URL`. -3. [Add this Action as a step][job-step] to your GitHub workflow and set the - input payload to send. +3. [Add this Action as a step][job-step] to your GitHub workflow and provide an + input payload to send to the webhook. 4. Configure your Slack workflow to use the payload variables sent from the GitHub Action. You can then update the steps of the Slack workflow to use these values in creative and clever ways. @@ -144,8 +144,8 @@ setup should be similar for all methods: **OAuth & Permissions** page. 5. Add the token as [a repository secret][repo-secret] called `SLACK_BOT_TOKEN` or something similar and memorable. -6. [Add this Action as a step][job-step] to your GitHub workflow and set the - input payload to send. +6. [Add this Action as a step][job-step] to your GitHub workflow and provide an + input payload to send as a message. Methods that require an app configuration token should gather this token from the [app configuration token][config-tokens] settings instead of from a specific