-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow passing optional arguments to chat.postMessage #268
Comments
Hi @knkarthik! Certainly a reasonable request. We've labeled this as a good first issue for the community (so feel free to tackle this yourself), else we'll see if we can find time after the holiday break to introduce it. 🙂 |
Hi, I've just had a look at this with an intention of implementing it, but there's no need! @knkarthik you can pass optional arguments as part of the Using
|
@laimonasA Thanks for investigating this! Just to confirm, would this also work if the payload uses block kit? Something like:
|
@knkarthik Yes, I've got something similar and it works for me |
@laimonasA, suppressing unfurling does not appear to work for me while using Slack Workflow Builder & Webhook.
I tried with The only time Slack does not unfurl the URL is when it is the same as the one I just sent. Any suggestions? |
Apologies @pashcan but I'm not sure how Slack Workflow Builder works in this situation, inspecting the code for this workflow it looks like the payload should be getting sent as expected. Having a quick look at this: https://api.slack.com/reference/messaging/link-unfurling I would be looking in the configuration for the app (or permissions), and I don't think the unfurl variables need to be included in the payload of your workflow. I hope that helps |
After some additional poking around, I discovered that our slack workflows were of the unmigrated legacy kind. Config to suppress unfurling works with the new workflow! 🎉 Knowing that it should be possible gave me the determination to continue looking. Thank you @laimonasA 🙏 PS: For anyone else stumbling onto this before the legacy workflows are fully deprecated in Sept 2024, the easy way to tell which one you have is by looking at your webhook URL: legacy ones use |
Description
chat.postMessage
has several useful optional arguments. Please support them! Personally I'm interested inunfurl_links
andunfurl_media
so that I can turn the auto-unfurl off for my use-case. Right now I've to roll my own version of this or use other actions that supports passing there arguments.What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:
Expected result:
What you expected to happen
Actual result:
What actually happened
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.
The text was updated successfully, but these errors were encountered: