Skip to main content

Below is a transcript of the conversation i had with the Zapier AI about this subject. Does anyone know if this is possible to achieve? 
___
“is it possible to setup an automation that doesn't require paths for dynamic account sending. Here's an example: if field_a = x, then I want to send information from zap connection A (EX: Gmail Account A), if field_a = y, then I want to send information from zap connection B (EX: Gmail Account 😎. These would be different accounts for the same action. (I would have shareable access for each account I'm wanting to send the information from.)”

 

“Yes, you can achieve this by using a single Zap with a filter step to check the value of field_a and then use different Gmail actions with the appropriate account connections based on the filter results.”

 

“right but wouldn't the different gmail actions require the "paths" function in Zapier to achieve this effect?”
 

“Yes, using Paths is the most straightforward way to handle different Gmail actions based on conditions like field_a values, as it allows you to branch your workflow and use different account connections accordingly.”

 

“if I have 25 different accounts based on 25 different variations of field_a, is there a way to more dynamically choose which account to use in a single zap step without spreading out into multiple paths?”

 

“Currently, Zapier doesn't support dynamically selecting accounts within a single step without using Paths. You would need to set up a separate path for each account or consider using a code step to handle the logic if feasible.”

Hi @risemodernwellness 

May depend on the specific app being used.

 

If you are using app APIs, then you can dynamically use variables to indicate the API keys, IDs, etc.

 

Some Zap app options:


Got it. One example would be for a Gmail APP connection. The other for a Ringcentral APP connection. Are you saying there is an alternative way to access the app APIs? I do not see an option for these fields directly within the config tab, this is forcing me to use the paths function instead.

The purpose of this desire is to be able to send content from a local account rather than a global account for personalization. 

Example: 

Ringcentral Account A is for store A with local telephone number A
Ringcentral Account B is for store B with local telephone number B
ETC
 

Doing the paths function for 5 stores is no big deal but it’s not really scalable once you get to 25+, 50+, 100+ in terms of simplicity. That’s the goal for looking for an alternative path.  

This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting.


@risemodernwellness 

Using the available Zap app triggers/actions, only 1 app account connection can be used in a Zap step.

 

There are advanced approaches using custom login and app APIs to make API requests dynamic.

Some Zap app options:


Got it. Good to know there’s an option as we scale! Thanks so much!


Great to see that Troy was able to help get this answered, @risemodernwellness! Thanks so much @Troy Tessalone! 🧡

I’ll mark Troy’s latest reply as the best answer so it’s easier for others to find. If you have any more questions, feel free to reach out. In the meantime, happy Zapping! ⚡️


Reply