Human In The Loop (Slack) Cannot Update Approve/Disapprove Button After Interaction

[tjbiddle]

Describe the problem/error/question

Human In The Loop Slack message does not update, and is unable to be updated.

When sending one of these messages, N8N creates a message and an ‘Approve’ or ‘Decline’ button as you wish. I’m able to approve/decline properly, and it goes to the baked-in webhook that N8N creates for it - however, the output is only approved:true or approved:false

Since no message ID about the original message with those buttons is returned, I’m unable to update Slack to inform that someone has pressed one of the buttons - so the buttons continue to say “Approve” or “Decline” - and Slack just presents an error about not being able to handle the payload.

N8N needs to provide the Channel ID and Message Timestamp so I can update the initial message.

What is the error message (if any)?

Slack cannot handle payload. If you know payload is formed correctly, file a ticket with /feedback.

Please share your workflow

Share the output returned by the last node

approved:true or approved:false

Information on your n8n setup

• Running n8n via n8n cloud, desktop app):

[Gallo_AIA]

Hello @tjbiddle welcome to the community!

I also bumpt into the same issue some days ago.
as far I know, n8n’s Slack “sendAndWait” does not return the channel or ts (timestamp) of the message, so there’s no way to update or replace the original message after an approval/decline.

At the moment, you can’t update the message after button clicks using the built-in Slack “sendAndWait”.
To achieve that behavior, you’d need to handle Slack messages and interactivity manually via the Slack API and webhook setup.

Alternatively, I suggest using the Telegram node because it is much simpler. I know it’s not the same, but I can assure you it works.

[King_Samuel_David]

I think it because Reference: Interaction payloads | Slack, and the app needs interactive responses.

I used a flow like below, to ask follow up questions, based on first input, and used ts or the orginal post, this flow would reply to that orginal post and await reply on that thread, checking the post number to increase. Not sure if that helps but thought too share.

[tjbiddle]

@Gallo_AIA

Hello @tjbiddle welcome to the community!

I also bumpt into the same issue some days ago.
as far I know, n8n’s Slack “sendAndWait” does not return the channel or ts (timestamp) of the message, so there’s no way to update or replace the original message after an approval/decline.

At the moment, you can’t update the message after button clicks using the built-in Slack “sendAndWait”.
To achieve that behavior, you’d need to handle Slack messages and interactivity manually via the Slack API and webhook setup.

Alternatively, I suggest using the Telegram node because it is much simpler. I know it’s not the same, but I can assure you it works.

Thanks!

And yeah - it doesn’t send those; which is silly. Seems like if N8N just updates that module though, then we’d be all good and this would work?

My business runs on Slack, so I’m not going to switch over to Telegram just for this unfortunately.

@King_Samuel_David

Not sure if that helps but thought too share.

Thanks! I don’t think it’s entirely applicable, but does seem to lean toward the same answer of “Sorry - doesn’t work with the N8N module, gotta do it yourself” lol.

Seems like N8N just half-baked this; which is a shame because this is my first experience with N8N and I immediately run into limitations and issues.

[Gallo_AIA]

Ehy @tjbiddle,
i understand the difficulty but n8n is a platform that updates a lot and continuously.

My suggestion is not to abandon her so quickly. In fact, your experience could help to improve it because your case could teach a lot.

Summarize your issue on Feature Requests.
Itìs the first step to improving what’s wrong.

[tjbiddle]

@Gallo_AIA Thank you - I’ll do that.Was about to, but looks like someone else already did. I upvoted and commented.

Could you please do the same, if you feel it’s worthy?

Include Slack Message Information in sendAndWait Response Output

The idea is: I would like the n8n Slack node’s sendAndWait functionality to include the original Slack message information in its output, alongside the form data it currently returns. Specifically, I want to receive the same response object that is returned by the Slack postMessage API when using sendAndWait. My use case: I am currently using the Slack node’s sendAndWait functionality to send messages and collect responses. While the node correctly returns the form data when a response is recei…

@King_Samuel_David you as well

Thanks, cheers.