Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hi all,

My first post here!

I’m running into a bit of an issue with attached images for the ‘’push to zapier’’ feature within Slack. I’m trying to build a workflow which is automatically generates an Instagram story based on an article URL in Slack. Now before I used an RSS scraper to scrape the image URL, but due to our image compressor the quality of image is too low to use for portrait stories.

What I want to do now is that our team can drop an image/video in Slack, which then will be used as an input for our content generator. The ‘’Push to Zapier’’ function seems to be the only way, as the file first need to be made publicly available by clicking on generate external link within slack before the Zap is triggered.

Now here is why I run into a problem. While drafting the workflow I can only use the one test message which is provided by Zapier. Unfortunately, this message does not (seem) to include a (public) file and therefore does not include a public file permalink in the output data.

This for example would be available if I would test using my own message by using a ‘’new message in channel’’ trigger (which I tried first), but then the zap starts running before the file is public, so it isn’t an option.

I know Slack provides a public permalink for files when using ‘’push to zapier’’ as I checked the output of my own messages on a live Zap. But right now I can't find a way to access this data as an input while drafting the workflow.

Based on this I have two questions: 

  1. Is there any way for me to test with my own ‘’push to zapier’’ message instead of the test message?
  2. Is there any other way to access the images permalink? I’ve also tried the find message method, but leads to same results as the test message does not contain any files. 

I’ve read this post were the file url is added in the message field, but I want use this field for another input and also minimizing the manual steps our team has to do. 

Once I've got acces the permalink my entire flow is working, so it’s the last piece of the puzzle. 

 

Hope somebody is able to help.

 

Thanks! 

 

Edit: Appologies for the terrible title, I pressed to soon on publish.

Hey @ThierryJB!

Some other things you could try:

  • Creating a workflow in Slack and send to Zapier that way (I didn’t see how you were ultimately trying to complete your Zap...like what’s the final action app/step). So, the action you need may or may not be available under workflows.
  • Would it work to use an emoji reaction as the trigger? Do you get the data you need if you try that method?

You also mentioned that you saw the data you need in a live Zap. Could you provide a screenshot of that?

Actually, another idea.

If you’re getting the field you need when the Zap runs live, there’s a way to “fake” a field. We have an article about it:

 

See if that works for you!

Hi @nicksimard 

That did the trick for me. I have to skip the testing phase, but with a live Zap it ended up working for me. 

I’ve just run into another problem, which is that no one Slack team have access to the Zaps I've created. I’m the only one that is able to acces my zaps through the Push to Zapier feature in Slack. Is there a way to make it available for all users in my Slack workspace?

Great to hear that my suggestion worked :)

As for granting access to that Zap to others in your Slack org, I’m afraid that’s not currently possible:

 

Could one of my initial suggestions for alternate triggers help out in this case, or not so much?

 

Terms & Conditions