Wave
Read and create Wave invoices, customers, products and transactions for your Wave business.
Connect it with: Sign in (OAuth), API key. Wave's own documentation: https://developer.waveapps.com/hc/en-us/articles/360019493652-OAuth-Guide.
What agents can do
Connect Wave so the agents working your tasks can reach it. With it connected, they can:
- List unpaid and overdue invoices and the customers who owe them.
- Draft an invoice from a task's line items for a person to review and send.
- Add or update customers and the products or services you sell.
- Record a payment or an expense against the right account.
Before you start
- A Wave business on an active Wave Pro or Wave Advisors plan: Wave turns off API access for businesses on the free Starter plan.
- A Wave login that can reach the business agents should work in.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Wave
This is the quickest way in: you sign in to Wave and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for Wave and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect Wave. Wave's sign-in window opens.
- Sign in to Wave if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at Wave yet. Use an API key, or your own OAuth app, until it does.
Scopes Jaah requests
Jaah asks Wave for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
| Scope | Why Jaah asks for it | Required |
|---|---|---|
user:read | Read who connected, so Test can name the account | Yes |
business:read | Read the businesses the account can reach, so agents pick the right one | Yes |
customer:* | Read and update customers when an invoice needs one | No — you may untick it |
invoice:* | Read, draft and send invoices | No — you may untick it |
product:* | Read and update the products and services invoices are built from | No — you may untick it |
account:read | Read the chart of accounts, needed to categorise transactions | No — you may untick it |
transaction:* | Record money transactions such as payments and expenses | No — you may untick it |
Connect with an API key
Prefer this when you cannot sign in with Wave — for example a service account, or a token your admin issued. On the Connect screen select Use an API key instead.
Find each value first:
- Full access token: Sign in at the Wave developer portal (developer.waveapps.com), open Manage Applications, select your application (create one named Jaah if you have none) and select Create token. Wave shows the token once. It reaches every business your Wave login can, so prefer the sign-in button for shared use.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Wave card.
- Name the secret and choose who can use it.
- Select Use an API key instead.
- Fill in Full access token.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Register your own OAuth app at Wave when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in Wave's developer console, https://developer.waveapps.com/hc/en-us (Wave's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new Wave secret, select Use your own OAuth app, paste both values and select Connect Wave.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah calls Wave's API once (POST https://gql.waveapps.com/graphql/public) with the stored values, and shows who it answered as, or which value Wave refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
A key connection hands the agent its fields: full_access_token.
Tell the agent in your task description which secret to use, for example “use the Wave secret org/wave”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Wave once the test passes. Steps: Replace or delete a secret.
- Reconnect: when Wave ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Wave's side too, revoke Jaah in Wave's settings, or revoke or delete the key at Wave.
Limitations
- When a business's Wave Pro plan lapses, Wave refuses to renew the connection and the secret shows Needs reconnect.
- A full access token reaches every business the Wave login can see; the sign-in lets you grant fewer scopes.
- Write scopes in Wave do not include reading: an agent that writes invoices also needs invoice:* rather than a write-only scope.
- Agents can do only what the connected Wave account and its granted scopes allow.
Troubleshooting
Test says Wave rejected the access token (UNAUTHENTICATED)
The token expired, was revoked, or the business's Wave Pro plan lapsed. Select Reconnect, or create a new full access token and select Replace.
Allow access is greyed out on Wave's sign-in screen
The business is on Wave's free Starter plan. Upgrade it to Wave Pro, then connect again.
An agent cannot find the business it should work in
The connected Wave login is not a collaborator on that business. Invite it in Wave's Settings > Users, then reconnect.
Still stuck? Select Test and read the result: it names the value Wave refused and the status it answered.
FAQ
Sign in or full access token?
Sign in for anything shared: it asks only for the scopes you tick and can be revoked from Wave. Use a full access token only for a quick personal test.
Does Test change anything?
No. It reads the connected user's email address and nothing else.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Wave account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.