Skip to content
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

Capture the response after sending a message #250

Open
chandrakanthkannam opened this issue Jan 4, 2024 · 1 comment
Open

Capture the response after sending a message #250

chandrakanthkannam opened this issue Jan 4, 2024 · 1 comment
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@chandrakanthkannam
Copy link

Hi,

I have been using this module to send out message cards, using this send function, which is creating a thread in a channel. I'm trying to capture the response of this message to identify my initial post and reply on that message, is it possible somehow?

@atc0005 atc0005 added help wanted Extra attention is needed question Further information is requested labels Jan 12, 2024
@atc0005
Copy link
Owner

atc0005 commented Jan 12, 2024

Hi @chandrakanthkannam,

When this library submits a given message (to a target webhook URL) the response received is very limited:

go-teams-notify/send.go

Lines 63 to 65 in 64c5cd4

// ExpectedWebhookURLResponseText represents the expected response text
// provided by the remote webhook endpoint when submitting messages.
const ExpectedWebhookURLResponseText string = "1"

This is enough to get a general sense of whether the payload was successfully delivered by this library, but not where it was delivered (e.g., what channel).

If you learn of a way to validate that using webhook connectors please share as others could benefit from that knowledge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants