LearnTutorial

Get exchange rates in Zapier with Webhooks by Zapier

Build a Zap that fetches current FX rates with Webhooks by Zapier, maps the JSON fields, and sends the observation to a spreadsheet, CRM, or notification.

8 Sep 2026 · 5 min read

Use a GET request in Webhooks by Zapier and ask for every needed currency in one symbols parameter. Webhooks by Zapier is a Premium app on Zapier’s current plan list. Test anonymously first, then store the bearer key in Zapier’s authentication fields instead of placing a secret in a URL or a visible step.

  • Use Webhooks by Zapier’s GET event; Webhooks is a Premium Zapier app, so check that your plan includes it before building the workflow.
  • Request multiple currencies together with /v1/latest/USD?symbols=EUR,GBP,JPY.
  • Map rates.EUR, source, market_session, and data_updated_at into later steps.
  • Keep the API key in Zapier’s authentication configuration and test with a placeholder value.

Create the trigger and webhook step

Start with the trigger that should refresh the rate, Schedule by Zapier, a form submission, or an event from another app. Add Webhooks by Zapier → GET, then use the URL below. One request can return all currencies your next step needs.

zapier · GET URL
https://api.exchangerate.dev/v1/latest/USD?symbols=EUR,GBP,JPY

Add authentication without exposing a key

For the first test, leave authentication empty and inspect the response. For a keyed Zap, configure the request header Authorization with the value Bearer {{your_key}} through Zapier’s supported authentication or custom-header fields. Never paste a production key into a public URL, a shared screenshot, or a sample Zap.

http · optional header
Authorization: Bearer exr_live_your_key

Map the response into the next action

After Test step, Zapier exposes nested fields from the JSON response. Map rates.EUR or another requested symbol into the destination, and keep source, market_session, and data_updated_at alongside it. Those fields tell a downstream report why a value may be daily rather than intraday.

  • Spreadsheet: write the rate, base, quote, and observation time to one row.
  • CRM or invoice draft: use the rate for an estimate, then let the payment provider determine settlement.
  • Notification: include the source and timestamp so the message is not mistaken for a live dealing quote.

Choose a schedule and handle failures

A daily report needs one scheduled call; an hourly dashboard uses about 720 calls in a 30-day month. Keep all symbols in one request. If Zapier receives 401, fix authentication. If it receives 429, reduce the schedule or account for the plan limit instead of creating an immediate retry loop.

Do not use a Zap as a settlement engine

These are indicative rates for automation, estimates, reporting, and analysis. A payment or regulated transaction should use the responsible provider’s executable quote and settlement record.

Questions

Do I need to build a Zapier app?

No. Webhooks by Zapier can make the GET request and pass the JSON to the next action, but the Webhooks app is a Premium Zapier feature on the current plan list.

Can a Zapier request use several currencies?

Yes. Add comma-separated codes to the symbols query parameter and map the returned rates fields.

Where should I keep the API key?

Use Zapier’s authentication or header configuration. Keep the key out of the URL, code examples, screenshots, and shared Zap data.

Can I use the free plan for a scheduled Zap?

Yes, within the published request limits. A daily job uses about 30 calls in 30 days; an hourly job uses about 720.

Keep reading

Start with a free API key

5,000 requests a month on the free plan. No credit card.

Get a free key