Best answer

New Row in Google Sheet to update multiple contacts in CRM/Email Apps


  • Anonymous
  • 0 replies

I have a unique situation where I have multiple (measured in 10’s to 100’s) of users that need to update multiple destinations with new data. This data is gathered ad hoc and can land in a Google Sheet when collected. I need to get that data OUT of the Google Sheet and INTO several software applications for each individual.

 

Example:

User A & User B have new contacts. They enter the details into Google Sheet (source). This Source data needs to be added to:

CRM (Zapier enabled)

Email Marketing Company (Zapier enabled)

Ad Target Lists (Zapier enabled)

 

and assigned to the relevant user.

 

I can add a column in Google sheets to pass a variable (username, etc) to key against. My thought is that Zapier would parse each new spreadsheet row, identify the user, and run a zap built FOR THAT USER that has all of the downstream API, Login, etc info. 

 

Is this a thing? 

icon

Best answer by Anonymous 29 May 2021, 22:31

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

Userlevel 7
Badge +14

Hi @kennethjamaca 

Yes, that’s the power of dynamically mapping data points between Zap steps.

Please reference this article about Zap action steps: https://zapier.com/help/create/basics/set-up-your-zap-action

FYI: App APIs can be used via Webhook action steps in Zaps: https://zapier.com/apps/webhook/integrations#triggers-and-actions

FANTASTIC! Follow up question… who can I hire to set this up for me? :grin::sunglasses:

Userlevel 7
Badge +14

@kennethjamaca

Check out Zapier Experts: https://zapier.com/experts

TIP: Put together documented project requirements (e.g. in a GDoc) that can be shared for review by whomever you are trying to hire for the job.

****SOLVED****

 

So, the best answer to my question was answered directly by a Zapier Expert (David Mercer from Mercology). He informed me of the Zapier Filter Action. This allows me to filter out the primary key (email address) and run a distinct zap for each user. Filter saved my sanity.