HumDay

Automate reverb

HumDay reads reverb’s own published API description and derives 163 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate reverb

What reverb is

reverb

API host: api.reverb.com

What HumDay can do in reverb

62 documented operations change something in reverb. The 36 most useful are listed here.

What HumDay can read from reverb

These are the operations a schedule or a trigger can watch.

How automating reverb works

  1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
  2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
  3. See it proven. The program runs and shows you the result before it is allowed near your live reverb account.
  4. Grant access, then go live. You approve the specific reverb operations it may use — and only those.

Popular reverb integrations

Connect reverb to the tools people pair it with most.

Automate reverb with these

Categories

Questions about reverb automation

Can HumDay connect to reverb?
Yes. HumDay reads reverb's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 163 operations are documented.
Do I need to write code to automate reverb?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your reverb account.
What can HumDay do in reverb?
62 of the 163 documented operations change something in reverb, and 101 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my reverb account safe?
Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to reverb is held behind that approval.

Where this came from

The operations above are read from a published API description for reverb at s3.amazonaws.com/swagger.reverb.com/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.