Why Does Pipedream Connect Only Send the First Block in My Array of Blocks to Slack?

Help
1

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

hi everyone, I’m using pipedream connect (free plan) to send block kit messages to slack. however, it only sends the first block in my array of blocks. I’m pretty confident it’s not an issue with my blocks because if I use the pipedream workflow builder with the same blocks, it sends all of them correctly - anyone experienced this and know what the issue could be?

2

Which tool/action are you using?

3

From Slack

4

I tried this with both Build and Send a Block Kit Message on Slack and Send Message (Advanced) from Slack API and experienced the same issue mentioned above

5

When using Send Message (Advanced), what is the full API request you’re sending (remove sensitive info)

6

Well actually can you share the request for both tools

7

configured_props = {
“slack”: {“authProvisionId”: auth_provision_id},
“text”: text,
“conversation”: channel,
“thread_broadcast”: False,
“unfurl_links”: False,
“unfurl_media”: False,
“passArrayOrConfigure”: “array”,
“blocks”: blocks, # array of blocks
“mrkdwn”: True,
“username”: “…”,
“icon_url”: “…”,
“as_user”: False,
}

for both I added relevant external_user_id and action_id, headers, etc.

8 
    config = get_pipedream_config()
    bearer = await _get_access_token()
    
    async with httpx.AsyncClient(timeout=10) as client:
        resp = await [client.post](http://client.post)(
            f"{PD_BASE}/connect/{config['project_id']}/actions/run",
            headers={
                "Authorization": f"Bearer {bearer}",
                "X-PD-Environment": config["env_mode"],
                "Content-Type": "application/json",
            },
            json={
                "external_user_id": external_user_id,
                "id": action_id,
                "configured_props": configured_props,
            },
        )
9

Hmm looks all right from a quick inspection

10

thanks - does that mean it’s an issue on the pipedream side? this is key functionality for my use case :disappointed:

11

Probably not, still checking

12

Does it send what’s in text or blocks[0]?

13

in the preview it shows what’s in text and then the blocks just show block[0]

14

Would you mind:

  1. Create a workflow with the code you’re using (values can be hardcoded just so I can test and run it)
  2. Reach out to support and share the URL for the workflow and I’ll try to repro with the same code