actions
actions copied to clipboard
looker-open-source
Support sending one webhook per row for zapier
Right now our zapier integration sends the entire payload in a single webhook. I'd like an option to send one web-hook to zapier for each row of the data.
Current workaround: Send the whole payload to Zapier, and write a python step in zapier that parses through the rows and fires off the remaining steps for each row.
Current limitations: Zapier can only trigger 250 new zaps on it's own, so this strategy doesn't work for datasets larger than 250 rows Writing python isn't particularly user friendly, and is very time consuming
Use cases:
- Sending each row of a Look to a different slack channel or recipient (based on a slack channel id or user id in each row of the data)
- Update a different sfdc record for every row in a look
Great feedback. Would it make more sense to sunset sending the result set and replacing with the row by row?
On Wed, Dec 6, 2017 at 2:26 PM Zev Lebowitz [email protected] wrote:
Right now our zapier integration sends the entire payload in a single webhook. I'd like an option to send one web-hook to zapier for each row of the data.
Current workaround: Send the whole payload to Zapier, and write a python step in zapier that parses through the rows and fires off the remaining steps for each row.
Current limitations: Zapier can only trigger 250 new zaps on it's own, so this strategy doesn't work for datasets larger than 250 rows Writing python isn't particularly user friendly, and is very time consuming
Use cases:
- Meta: Sending usage for every trial into each trial's slack channel (we are approaching 250+ open trials, so we're currently batching this into multiple sends from Looker)
- Meta: Send hourly alerts into slack channels when prospects/customers connect their instance to a database or add new users
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/looker/integrations/issues/93, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdDJdnNx-jq84jboPgxCnKxKiIL9W68ks5s9xSKgaJpZM4Q4sEm .
Perhaps some of this is better solved by improvements to the Slack action or a Looker-internal action hub that we can use for our own custom actions?
@jdavidson i think there are valid uses cases for both sending the whole dataset, or sending rows individually. If I had a Look with one column and 10 rows, I might want to send that whole thing into a single zap.
@wilg Zapier has an extensive library of integrations, and you can use it to string together interactions with multiple tools via a simple UI in ways I doubt the action hub will support in a way that a non-developer could use.
For example:
I have a scheduled look that sends out a list of all new zendesk tickets in the last hour, and sends alerts to the appropriate account rep via slack. Our ETL is scheduled hourly, but fails about 10% of the time (and missed tickets are added in in the subsequent ETL job). In this scenario, it's difficult to ensure that Looker sends tickets out once and only once. Instead, Looker always sends the last 6 hours of tickets (to ensure we don't miss any), and Zapier takes care of preventing duplicate slack messages.
Happy to show you what I'm doing with Zapier today if you'd like!
Yea I'm sure there will be great uses for Zapier, just wondering if there's a neat way to cover your use case directly and not require people to go through that complex set up process.
+1 @talal-assir who is using Looker + Zapier to update the topic of multiple slack channels
+1. Customer wants to use Looker webhooks to create tasks in Salesforce in bulk, and this would simplify the setup a little.
