I’m having the same issue as this old one, but in my case when the Zap is turned on, other Slack Team members with Zapier connections still cannot access the Zap.
I am using the Push From Slack Message trigger but it only works for whoever owns the Zap and won’t show up for anyone else in the same team. I’ve tried a variety of things like making sure the creator is an Admin, and has set their Slack team connection to share with everyone.
The Zap itself works if the owner triggers it.
I can’t figure out what I am missing in the setup.
Best answer by SamBBest answer by SamB
Hey folks,
Reaching out here to share that the feature request has been implemented! 🎉
Thanks so much for everyone patience on this. In case you missed the email notification, here are the important details from it:
“When configuring your Zap's trigger, you can choose between three "access types". These options enable you to specify which Slack users should be allowed to trigger your Zap from within Slack, and include: "only me", "specific users" and "anyone in my workspace".
In order to facilitate this change, we've fundamentally updated the way that Zapier communicates with Slack behind the scenes. This means that if you were previously using the "New Pushed Message" trigger, your existing Zaps are currently unaffected and won't see these updates just yet. However, we're actively working to update them very soon, so that there'll be no action required from you. Of course, you're also able to access this new feature right now when creating new Zaps with the Slack integration.”
Before you get started Do you have restricted apps on your Slack workplace? If you’re not sure, you can check if Slack is one of them in your restricted apps on your Slack workspace. It may be the case that you need to get approval from your Slack admin to approve Zapier.
Once you are sure Zapier is an approved app, move onto the following steps:
I too would like to share a common Zap which is triggered by a Slack push with multiple members of my team. Previously we’ve had to copy the Zap and modify each copy to update each Slack step to use each member of the team’s individual Slack accounts. With a large team, as you can imagine, this becomes very tedious and a burden especially if we update the template and then have to ask everyone to delete, copy, and then update again to get any changes.
Hi there, @JMcCann! Thanks for reaching out and sharing your feedback.
I took a peek and wanted to share what my teammate Nadia shared with @sblausten in their support email:
Right now, the "New Pushed Message" trigger for Slack will only work for the Slack account that's specified in the Zap.
This does mean that in order for the rest of your team to use this Zap, they'd need to create their own copy of your Zap, then change the connected Slack account to their own one.
The easiest way to do this would be to: 1) Invite your team to the Teams account (if they haven't joined yet) 2) Be sure those Push Zaps are in a Shared Folder that's shared with everyone, which will allow your colleagues to create copies of those Zaps. 3) In their own Zap copies, they will need to replace the Slack account to their own one 4) If they wish to keep their Zap Private, they can move it to their own Private Folders
I can certainly see how it would be super handy to be able to create a single Zap that's shared with everyone in the Slack org, though! We have a standing request for this improvement, and I've gone ahead and added your email as a vote. This way, we can automatically notify you if this does become available.
That said, I did go ahead and add you to this feature request as well! We’ll be sure to send you an email and update this thread as soon as we know more.
We use an internal tracking system for feature requests and bug reports so not something we’re able to share. That said, once an update occurs in terms of implementation everyone on the list will be notified via email. Our team will also be notified so we can update the thread. 🙂
Reaching out here to share that the feature request has been implemented! 🎉
Thanks so much for everyone patience on this. In case you missed the email notification, here are the important details from it:
“When configuring your Zap's trigger, you can choose between three "access types". These options enable you to specify which Slack users should be allowed to trigger your Zap from within Slack, and include: "only me", "specific users" and "anyone in my workspace".
In order to facilitate this change, we've fundamentally updated the way that Zapier communicates with Slack behind the scenes. This means that if you were previously using the "New Pushed Message" trigger, your existing Zaps are currently unaffected and won't see these updates just yet. However, we're actively working to update them very soon, so that there'll be no action required from you. Of course, you're also able to access this new feature right now when creating new Zaps with the Slack integration.”
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More about cookies
Customize which cookies to allow
Marketing cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Social media cookies
label
These cookies are set by a range of social media services that we have added to the site to enable you to share our content with your friends and networks. They are capable of tracking your browser across other sites and building up a profile of your interests. This may impact the content and messages you see on other websites you visit. If you do not allow these cookies you may not be able to use or see these sharing tools.
Analytics/performance cookies
These cookies enable the website to provide enhanced functionality and personalization, and allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. These cookies may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly and we will not know how you are using our site.
Functional cookies
label
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Essential cookies
Always active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.