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,

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:

 

 

Hi @hummus 

Good question.

Slack Channel fields expect the Slack Channel ID.

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!

@hummus 

Use a lookup table.

 

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 😎 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