About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

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

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

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.

Best answer

How do I Transform/Format Slack Channel Names?

  • 14 December 2023
  • 4 replies
  • 68 views
H

Hi,

Is it possible to do the following? I’m using “Translate by Zapier” to automatically translate Russian messages sent on ru- channels to en-channels to achieve this:

User sends message to ru-documentation channel
Zapier detects that message was sent on ru-documentation channel
Zapier re-formats ru-documentation channel name to en-documentation
Zapier sends message to en-documentation channel

I’m having difficulty transforming the ru- channel into a en- channel.

 

Action: replace “ru-” with “en-” in channel name:

 

But then I’m unable to use that re-formatted channel name to post a message:

 

 

icon

Best answer by Troy Tessalone 14 December 2023, 22:13

View original
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Troy Tessalone
Userlevel 7
Badge +14

Hi @hummus 

Good question.

Slack Channel fields expect the Slack Channel ID.

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
H

I understand. What’s the most efficient way to do an IFTTT for many different options?

If Channel ID = 111111, then replace for 123456
If Channel ID = 222222, then replace for 234567
If Channel ID = 333333, then replace for 345678
etc.

I think this could work with “Path by Zapier” but it seems quite inefficient.

Thanks for your help, Troy!

Troy Tessalone
Userlevel 7
Badge +14

@hummus 

Use a lookup table.

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
H

This was very helpful, thanks, @Troy Tessalone!

I created a Lookup Table and it worked – but I dug deeper and ended up creating a Zapier Table as the relationship I wanted to create (between Slack Channel A and Slack Channel B) could be useful for other Zaps. A Zapier Table was also more “admin-friendly” in this case as it allowed me to add a 3rd column (“Destination Channel Name”) used only for reference when I manually (for now) inputted the Destination Channel IDs. 

 

The Zapier Table:

 

And the settings to associate a Destination Channel ID based on a Source Channel Name.

 

 

Terms & Conditions