The unit of time for how often this trigger, e.g., choose “Days” for “Every three days”

The number that corresponds to your Frequency Type, e.g., enter “3” for “Every three days”. Decimals and negative numbers are not accepted.

Enter the date for when you want the trigger to run for the first time. The Frequency Type and Interval will be based off of this date. Use the format YYYY-MM-DD, e.g., 2024-02-28 and Time of Day is 6:30 AM. The Zap will trigger on the date 28-Feb-2024 6:30 AM.

Enter the time of day when you want this action to trigger. Use the 12-hour format with AM/PM. For example, `6:15 PM`. This Zap will trigger according to your account-level [timezone settings](https://zapier.com/es/app/settings) . If you haven't set a timezone, it will default to UTC (GMT+00:00). Zap-level timezone settings will not apply to this trigger.

Enter a valid IANA timezone (e.g., America/Los_Angeles, Australia/Sydney). This overrides your account-level timezone for this Zap only.

Should this Zap trigger on Saturday and Sunday?

This Zap will trigger once every hour at your chosen offset past the hour. For example, choosing `15` will schedule your automation to run at 1:15, 2:15, 3:15, etc. By default, this Zap will trigger at the top of the hour.

Choose the day(s) of the month you want this Zap to trigger. You can select multiple days. Please note that if you choose a day that does not exist in a particular month (like the 30th or 31st in February), the Zap will not trigger for that day in that month.

Schedule is a native Zapier app you can use for recurring tasks. Trigger an action every day of the month, every day of the week or every single day. You can also select the hour of the day. If you're a developer, this is similar to a crontab, cronjob or cron.

Schedule by Zapier

IQM Reports provides access to all dimensions and KPI of your ad-serving reporting data in convenient file formats.

IQM Reports

By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given `{"contact": {"name": "Mike"}}`, add "contact" here to only return `{"name": "Mike"}`. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.

This should return a list of dictionaries of content type JSON in reverse chronological order. For example: `[{"id":1234},{"id":1235}]`

If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)

Zapier deduplicates the array we see each poll against the `id` key. If the `id` key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with `id` in it otherwise we will raise an error.

If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!

A pipe (`|`) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

The HTTP method we'll use to perform the request.

Any URL with a querystring will be re-encoded properly.

If yes, request `data` below will be overridden with the raw data from the previous step (you are still responsible for headers though, like `Content-Type`). Defaults to no.

Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data `Content-Type`. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

Returns the raw response from the request, in the following keys: response, status, headers. Ignores `Unflatten`.

We recommend *not* putting any query string arguments in the URL (use "Query String Params" below).

These params will be URL-encoded and appended to the URL when making the request. *Note:* If you specify nothing for this field, **we will automatically encode and include every field** from the previous step in the query string. If you don't want this, use the "Custom Request" action.

If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the **Custom Request** action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to `multipart/form-data`, with the above payload type defining the sub content-type for the data being passed.

Webhooks simply POST data (or JSON) to a specific URL every time we see something new. Webhooks can also accept data (or JSON) to kick off a workflow in Zapier.

Webhooks by Zapier

Use webhooks to collect your weekly ad-serving reports to one place! With this integration, your weekly IQM ad-serving report will automatically be sent to a webhook URL of your choice, streamlining your workflow.

Schedule by Zapier + Webhooks by Zapier + IQM Reports

POST IQM ad-serving reports to webhook URLs every week

Supported triggers and actions

Custom Frequency

Every Hour

Every Week

Every Day

Every Month

Generate CSV Report

About Schedule by Zapier

Related categories

About Webhooks by Zapier

Related categories

About IQM Reports

Related categories

Related Zap Templates

Related Zap Templates