Skip to content
Heads up — these docs cover Voice Monkey API v3, the current version. If you signed up before the v3 launch, your account is still on API v2 for a limited transition period and the examples below will not work against your account.

Zapier

The Alexa Voice Monkey app on Zapier lets any Zap talk to your Echo devices: speak a message, show one of your Screens, trigger an Alexa Routine, run a Voice Monkey Flow or set a variable. No API tokens to copy — you connect your Voice Monkey account once with a secure sign-in, then pick devices and Flows from dropdowns.

  1. In Zapier, add an Alexa Voice Monkey step to a Zap and click Sign in.
  2. A Voice Monkey window opens. Sign in with Amazon if you aren’t already, then click Authorize Zapier.
  3. You’re returned to Zapier with the connection labelled with your Voice Monkey name.

Behind the scenes Zapier receives its own API token, hidden from your API tokens page. It keeps working until you remove the connection in Zapier (Apps → Alexa Voice Monkey → Disconnect), which stops Zapier calling your account. You can connect the same Voice Monkey account from more than one Zapier account.

Action What it does Voice Monkey API
Make Announcement Speak text (with optional voice, language, chime, audio, image, video, website or on-screen text) on a Speaker device. /announce
Show Screen Show one of your Screens on an Echo Show, Echo Spot or Fire TV, optionally saying something and setting variables first. /announce
Trigger Routine Fire a Routine Trigger device so the Alexa Routine wired to it runs. /trigger
Run Flow Start one of your Flows by name, optionally overriding the device and setting variables first. /flow
Set Variable Create or update a variable for use in Flows and announcements. /variables

Every text field accepts Zapier data from earlier steps, so an announcement can read out the subject of an email, a calendar event title or the value from a form submission.

Pick the Speaker from the dropdown (only devices with the Speaker capability are listed) and enter the Speech. All other fields are optional and map 1:1 to the Announcement API parameters:

  • Voice — an Amazon Polly voice ID such as Joanna or Brian.
  • Language — a BCP-47 code such as en-GB or de-DE.
  • Chime — a soundbank:// URL played before the speech.
  • Audio / Image / Video / Website URL — media to play or show on Echo Shows.
  • On-screen text — full-screen text on Echo Shows.

Announcements count towards your plan’s monthly request quota, exactly as a direct API call would.

Pick the Speaker and the Screen from the dropdowns (screens are designed on the Screens page in the console). Optional fields:

  • Speech — text to say while the screen appears.
  • Variables — key/value pairs saved before the screen is built, the same as passing var-NAME=value to the API. A screen showing {FRIDGE_NOTE} shows the value you send, so a noticeboard can display the subject of a new email or a form answer. Keys must be UPPER_SNAKE_CASE.

Clocks, dates, countdowns and slideshows on the screen keep updating on the device. Each run counts as one request, like an announcement.

Pick the Routine Trigger device. The Alexa Routine whose “When this happens” is that device runs immediately.

Pick the Flow from the dropdown (disabled Flows are shown but will fail with FLOW_DISABLED until you re-enable them in the console). Optional fields:

  • Device — override the device the Flow runs against.
  • Variables — key/value pairs to upsert before the Flow starts, the same as passing var-NAME=value to the API. Keys must be UPPER_SNAKE_CASE.

Enter the Name (UPPER_SNAKE_CASE) and Value. Reserved names (WEBHOOK, WEB_RESPONSE, VM, and anything starting with VM_) are rejected.

To start a Zap from Alexa:

  1. In Zapier, create a Zap whose trigger is Webhooks by Zapier → Catch Hook and copy the hook URL.
  2. In Voice Monkey, build a Flow with a Web Request node that POSTs to that URL (you can include {VARIABLE} placeholders in the body).
  3. Run the Flow from an Alexa Routine, by voice (“Alexa, ask Voice Monkey to start flow 1234”) or via a Schedule.

If an action fails, Zapier shows the error from the Voice Monkey API in the Zap history:

Error Meaning
DEVICE_NOT_FOUND / FLOW_NOT_FOUND / SCREEN_NOT_FOUND The device, Flow or Screen was deleted since you built the Zap. Re-select it in the step.
FLOW_DISABLED Enable the Flow on the Flows page.
MONTHLY_QUOTA_EXCEEDED Your plan’s monthly request budget is used up. Wait for the period end or upgrade.
THROTTLED The per-account safety lockout is active; Zapier will retry the step later.
INVALID_TOKEN The connection was revoked (for example after the account was deleted). Reconnect the app in Zapier.

You can also skip the app entirely and call the API from Webhooks by Zapier with a token from your API tokens page — see the API overview. The native app is simpler to set up and keeps your tokens out of Zap configuration; the webhook route exposes every API parameter.