Connect bunq and Google Sheets
Describe what you want to happen between bunq and Google Sheets in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
bunq
421 documented operations. See all bunq operations
- POSTCreate a new DeviceServer providing the installation token in the
/device-server - POSTCreate a new session for a DeviceServer
/session-server - POSTCreate a new public attachment
/attachment-public - POSTUsed to create a sandbox userPerson
/sandbox-user-person - POSTCreate a new debit card request
/user/{userID}/card-debit - POSTUsed to create a sandbox userCompany
/sandbox-user-company
Google Sheets
17 documented operations. See all Google Sheets operations
- POSTCreates a spreadsheet, returning the newly created spreadsheet
/v4/spreadsheets - POSTApplies one or more updates to the spreadsheet
/v4/spreadsheets/{spreadsheetId}:batchUpdate - POSTReturns the spreadsheet at the given ID
/v4/spreadsheets/{spreadsheetId}:getByDataFilter - POSTCopies a single sheet from a spreadsheet to another spreadsheet
/v4/spreadsheets/{spreadsheetId}/sheets/{sheetId}:copyTo - POSTClears one or more ranges of values from a spreadsheet
/v4/spreadsheets/{spreadsheetId}/values:batchClear - POSTSets values in one or more ranges of a spreadsheet
/v4/spreadsheets/{spreadsheetId}/values:batchUpdate
How a bunq and Google Sheets automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in bunq and Google Sheets, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- bunq and OData for namespace microsoft.graphintegration
- Google Sheets and OData for namespace microsoft.graphintegration
- bunq and Cloudflareintegration
- Cloudflare and Google Sheetsintegration
- bunq and NetBoxintegration
- Google Sheets and NetBoxintegration
- bunq and GitHubintegration
- GitHub and Google Sheetsintegration
- bunq and Mistintegration
- Google Sheets and Mistintegration
Questions about connecting bunq and Google Sheets
- Can bunq connect with Google Sheets?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect bunq to Google Sheets?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate bunq and Google Sheets?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across bunq and Google Sheets?
- bunq publishes 421 documented operations and Google Sheets publishes 17. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either bunq or Google Sheets is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for bunq and Google Sheets. Descriptions are each provider’s own words, not ours.