New in Zapier Manager: Automatically share reports of your Zap’s activity

Categories: App Integrations Zapier Apps Product Updates
New in Zapier Manager: Automatically share reports of your Zap’s activity

Hi everyone, I’m a product manager at Zapier and I just wanted to announce a small feature we’re now beta testing to make it easier to keep tabs on what your Zaps are doing. 

“Create Zap Report” is a new action in the Zapier Manager app that can generate a report of a given Zap’s activity for the last seven days:

When it runs, the action will return the information about the Zap and summary data like:

  • Successful runs: The number of times the Zap ran without an error

  • Times triggered: The number of times the Zap triggered (whether or not it completed successfully)

  • Tasks used: The total number of tasks used by the Zap

  • CSV (file and URL): A CSV file with the raw data for each step (can later be used in fields that accept files, like an email attachment), and a URL to that same CSV

  • Start time: The beginning of the reporting period

  • End time: The end of the reporting period

All data is for the seven days prior to this Zap running.

To try this out, just use this Zap Template which uses Schedule to run every week on 9am on Monday and Email by Zapier to send an email with a pre-formatted message that looks like this:

 

You can customize the day of the week and time you want your Zap to run, choose the Zap you want to report on, and the body of the email and who to send it to. Maybe you want to send your boss a weekly report of how many leads came in based on the number of successful runs:

 

 

You could even replace the Email step with a later action of your choice, like adding the data to a Google Sheet or whatever else you want! By monitoring the Zaps that power your business you can generate high-level insights into how things are going, keep your team in the loop, and more. We’re excited to see how you use this!

For now, this action is only available via a Zap Template, so click here to get started.

If you have any thoughts or feedback on this action, including any requests for how we can make it better or ideas for how you’ll use it, please chime in below!

Ooo I’m always looking for new functionality within Zap Manager, so thank you @Noah Manger for working on this!

Question, why does it require a zap to be selected? Could we have it run for all zaps in a given folder, or in a given account? As an agency with multiple clients we want to monitor our client accounts and there are multiple (dozens) zaps running in each folder within each account, it would be cumbersome to create a monitoring zap for each zap. 


Thanks @PaulKortman ! That’s something we’ve been considering as a possible enhancement, and were curious if folks would want it. So glad to hear that would be useful! 


@Noah Manger to be clear it’s only useful for me/my agency. I suspect the average user wouldn’t need this feature, but I could see it becoming viable for a user who wants to watch their task usage very closely. on a daily/weekly level for example to ensure no overages… Or if they want to be alerted to anomalies like spikes in task usage...


Hi @PaulKortman !

In the meantime, one possible workaround for this would be to add a Looping by Zapier Step before the Create Zap Report Step with a comma separated list of the Zap IDs that you want to get reports for. By mapping the output of the loop value into the Zap field as a custom value, you could repeat the actions for multiple Zaps and send those reports where you need.


Ooo I’m always looking for new functionality within Zap Manager, so thank you @Noah Manger for working on this!

Question, why does it require a zap to be selected? Could we have it run for all zaps in a given folder, or in a given account? As an agency with multiple clients we want to monitor our client accounts and there are multiple (dozens) zaps running in each folder within each account, it would be cumbersome to create a monitoring zap for each zap. 

I agree.  For a Folder or individual zap


Thanks for the feedback, @pgonyon! I’ll be sure to pass along your thoughts and make sure your votes been counted for this feature. 🙂While we don’t have a time frame for when this could be available we’ll be sure to keep you and this thread in the loop if it does get implemented! In the meantime, it might be worth checking out the workaround my teammate TimS mentioned:

...one possible workaround for this would be to add a Looping by Zapier Step before the Create Zap Report Step with a comma separated list of the Zap IDs that you want to get reports for. By mapping the output of the loop value into the Zap field as a custom value, you could repeat the actions for multiple Zaps and send those reports where you need.


I would simply like to see the Task Usage information included in the daily Zapier Activity email report.

Include this and I’d be quite happy!

 


Hi all, 
 

I used the template linked above but I’m getting this error. 
Is the Beta for this functionality still active?

 

Thanks!

 


I’m getting the same error as LL-GOM. Are you able to resolve?


Also receiving the same error as above.

The latest message I’ve seen addressing this was back 11mo ago, has this feature been deprecated?


Same error here.


Same error. Maybe @Troy Tessalone knows what’s up?


Has this feature been deprecated? Seeing a lot of posts from almost 12 months ago and still no resolution? Can the Zapier team provide an update?


I’m trying to test it right now but I’ve got stuck. Apparently the Trigger part of this app is working. Except that when I try to pull the data for a test, instead of pulling an actual real data is giving me Generic Template data. (See Example Below):
 



My intention is to create a Zap that will automatically sends the Full Payload of “Data In” to a google sheet, every time an Stopped-Errored or Stopped-Halted occurs on a specific folder or Zap (See example below):
 


Right now, I can set the trigger (Zapier Manager + New Zap Error), I can set the Folder and or Zap, but when the system parse the data it’s not loading in Full (See first picture). And when its time to export the payload we are having the same problem since is not giving us access to the full payload of that error. 

Can you please advice if this will be solved, or if is there any workaround to allow us colleting the detailed error data? The main fields that will make sense to have it available so we can actually use this tool with purpose would be: 

Date of the Error/Halted: (Date Format)
Error Type: (Example as per picture: “The app returned: 502” )
Zap Name: (Text Format)
Zap ID: (Number or Text Format)
Zap Folder: (Text Format)
Error Link: (The same one you guys already send over the email)
Payload: (Same as “Data-In” - Or if you want to be really good for the community you could present these fields individually) 

I really believe that this should be a piece of cake for your developers, since you already have all the data recorded there (You even send us via email). So maybe its just a matter of mapping these fields so they can come on the Zapier Manager when we use it as a trigger….

Looking forwards to hearing from you. 


Hi,

Any lead when this feature will be back? i sent two tickets since last spring. I think this feature can help a lot of us that are trying to track the task/price from long complexe and multiple path zaps.

Thanks