Incomplete copy of multi-photo posts between channels
Im not sure I have my Zap set up correctly. When I post to my test channel and only add 1 photo to the message, it will correctly copy the message and photo to another channel. But if I create a post with multiple photos, it only copies the one and tries to add URL links to the others.
I need it to exactly copy the one message with all photos to another. Is there anyone that can help me out with this?
This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing sensitive details.
Page 1 / 1
Welcome @mf112! Thanks for joining our community!
I wonder if it’s only able to render a preview for the first image. Try moving the Attachments Url field, that’s currently in the Message Text field, down to the File Attachments field:
I’m thinking that should then allow it to correctly add each photo to the Discord message.
Can you give that a try and let me know how it goes?
Wonderful! Worked perfectly!
Wow! Thank you for confirming that Sam’s resolution got the Zap running. This will significantly help our Community members to have as a reference for the same issue.
I spoke too soon. After doing some further testing, on both a mobile device and a desktop, I receive “file lookup errors” instead of a picture. I'm not sure what's going on. See below.
It doesnt matter how many photos are sent or from which account. Still have File Lookup Errors.
Hi there @mf112,
It looks like the “File Lookup Error” is because of the attachment file type, which is a .txt file.
Could you please double check if the file from the trigger step is an image file?
I'll be keeping an eye out for your response!
Did some “Retest Step" option under the send channel message, and it came up with an error, calling the filename attachment.txt.
Not sure why the error, because under data in...it calls them all .jpg files See below.
Hi there @mf112,
Thanks for the additional details!
It looks like you might be running into a bug. To get this investigated further, I recommend reaching out to our Support Team—they have the right tools to dive deeper into your Zap and its logs.