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.

We are aiming to have a community which uses Slack for chat and Mighty Networks (which is already set up) for the repository of the content. This allows us to stay on the free version of Slack.

 

By using Zapier, we are able to pretty much replicate all posts which are added to MN spaces and repost them in Slack from the same user (allbeit not linked). But we’re having difficulties the other way. Any ideas?

 

In summary:

  • We have already connected our Slack and Mighty Networks
  • We have already configured a Zapier so that when someone sends a message to a MN space, it automatically posts the message on the related Slack channel and comes from the user as they appear in MN.
  • When we configure it so the messages do the same going the other way, ie if I post on a Slack channel I want the message to then be posted on the relevant MN space and the message to be posted by the person who posted it (pulling in their details from Slack, which happens the other way), not the admin or whoever’s MN account is connected to Zapier, as it does now.

 

 

Hi!

I’m afraid that won’t be possible since we are posting to Mighty Networks based on the user that created the connection.

One idea would be to create a generic user that you could connect to Mighty Networks. That will stop any personal information getting tied to the post itself. 

Let us know if you have any other questions.

Hi Shane,

 

Thank you for your response. That is as I suspected, which is a shame because into Slack it works find and can pull the name and profile picture from Mighty Networks. Is that just because Mighty Networks has more secure identity verification or something?

 

Your proposed solution is basically what we were settling on - having an admin called ‘Message from Slack’ and then having the name of the user in bold or something in the message to ensure its obvious.

 

Let me know if you have any other ideas but thank you anyway for your help.

 

Best,

Ryan

Reply


Terms & Conditions