Why am I encountering a deployment bug with Connect API triggering some Slack events?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

Found some bug with deploying triggers via Connect API.
Some Slack events are not deploying (returns 500 errors). E.g. slack-new-message-in-channels

Request:
curl --request POST
–url https://api.pipedream.com/v1/connect/proj_XXXXX/triggers/deploy
–header ‘Authorization: Bearer ’
–header ‘Content-Type: application/json’
–header ‘x-pd-environment: development’
–data ‘{
“id”: “slack-new-message-in-channels”,
“external_user_id”: “1”,
“configured_props”: {
“conversations”: “<channel_id>”,
“resolveNames”: false,
“ignoreBot”: false,
“ignoreThreads”: false,
“slack”: {
“authProvisionId”: “<app_id>”
}
}
}’

RESPONSE (500):
{“error”:“Unexpected error, please reach out to our team at Support - Pipedream”}

Tokens, and all ids are fine, because they work fine with other Slack events (no errors).
Can the problem be on your side?

2

I’m sorry you’re running into this issue deploying the slack-new-message-in-channels trigger via the Connect API. A 500 error indicates an unexpected server-side issue. Since your tokens and IDs work with other Slack events, it’s unlikely to be a problem with your credentials or payload formatting. Possible causes: - There may be a temporary or specific issue with the deployment of this particular Slack trigger (slack-new-message-in-channels) via the Connect API. - Sometimes, certain triggers require additional configuration or permissions that may not be needed for others. - There could be a bug or outage on Pipedream’s side affecting this trigger. What you should do next: - Double-check that the conversations value is the correct channel ID and that the Slack app has the necessary permissions for that channel. - Ensure the authProvisionId is valid and correctly linked to the external user. - Since other Slack triggers work, it’s likely not an auth issue, but you might want to try deploying the trigger manually in the Pipedream UI to see if it succeeds there. But most importantly: This error message specifically asks you to reach out to Pipedream support for help: > {“error”:“Unexpected error, please reach out to our team at Support - Pipedream”} Please visit Support - Pipedream and provide them with: - The full request payload (with sensitive info redacted) - The exact error response - Any relevant workflow or project IDs They’ll be able to investigate the server-side logs and help resolve the issue. If you have any more details or error logs, feel free to share them here, but for 500 errors like this, support is your best next step.

3

the same credentials work just fine with other Slack events, e.g. slack-new-direct-message

4

Try wrapping the wrapping the channel_id in an array:

    "conversations": ["<channel_id>"],
5

Try wrapping the wrapping the channel_id in an array:

"conversations": ["<channel_id>"],

> 
Yeah, that worked. Thanx a lot,