Does Storage by Zapier have the same single-instance limitation as other actions in Agents?

Hi ​@teel27, welcome to the Zapier Community 👋

Great question about Storage by Zapier and its behavior in Agents.

Yes, Storage by Zapier does have the same single-instance limitation as other actions in Agents.

When you add Storage by Zapier as a tool in an Agent, any configuration changes apply globally across all references to that action within the same Agent.

For storing multiple sets of authentication credentials within a single Agent, here are your options:

• Use different Storage keys
  • Storage by Zapier supports up to 500 different keys per Storage account. You can structure your keys to differentiate between different authentication contexts:
    • `auth_system1_username` and `auth_system1_password`
    • `auth_system2_username` and `auth_system2_password`
    • Or use prefixes like `prod_username`, `staging_username`, etc.
• Use Child Values for grouped credentials
  • Storage by Zapier supports child values for nested data. You can store related authentication data together:
    • Key: `system1_auth` with child values: `username` and `password`
    • Key: `system2_auth` with child values: `username` and `password`

Alternative approach without separate sub-agents: Use Code Steps with StoreClient

You can use Code steps (JavaScript or Python) with the StoreClient for more advanced storage operations. This gives you programmatic control over which credentials to retrieve based on context.

Hope this helps!

​@Sebastian M 

 thank you for taking time to assist me in this learning curve, I’ll try using the different storage keys.