Why connect themThe Routing Number Lookup API in Google Sheets.
Google Sheets is the go-to collaborative spreadsheet for teams worldwide. Connecting APIs to Google Sheets transforms your spreadsheets into dynamic, self-updating data hubs. Automatically populate rows with API responses, validate data in real-time, and create living dashboards that reflect the latest information.
What you can buildWorkflows worth wiring.
Automatically validate email addresses in a contact list and flag invalid entries
Build a real-time currency conversion tracker that updates exchange rates hourly
Create a lead scoring spreadsheet that enriches contact data with IP geolocation
Monitor domain SSL certificates and log expiration dates for your portfolio
TemplatesReady-made ideas.
New row added in Google Sheets Fetch routing lookup for routing number in row → write bank, city, state, and zip back to the rowValidate Routing Numbers in Google Sheets
When a routing number is added to a spreadsheet, automatically populate columns with the bank name, city, and state.
Scheduled periodic trigger Fetch routing lookup → append row with routing_number, bank, address, city, and state to Google SheetsBank Info Log in Google Sheets
Build a bank information log by recording routing number details including bank name and address.
SetupConnect it in a few steps.
Set up with Zapier
- 1
Set the trigger. Create a Zap with Google Sheets as the trigger app and "New row added" as the event. Connect your account.
- 2
Add the API action. Add APIVerve as the action, select the Routing Number Lookup API, and map your trigger data to the request.
- 3
Send it back. Add a second Google Sheets action for "Add row" and map the returned fields (like routing_number) into it.
- 4
Test & turn on. Test the Zap with real data to confirm the mapping, then turn it on.
Set up with Make
- 1
Add the trigger. Create a scenario and add a Google Sheets module set to "New row added". Authenticate your account.
- 2
Call the API. Add an HTTP module pointing at api.apiverve.com/v1/routinglookup with your x-api-key header. Pass the trigger's data as the input.
- 3
Parse & map. Add a JSON module to read the response, then a Google Sheets module for "Add row". Map fields like data.routing_number into place.
- 4
Activate. Run once to confirm the mapping, then switch the scenario on and set its schedule.
Set up with n8n
- 1
Add the trigger node. Start a workflow with a Google Sheets trigger node for "New row added" and connect your credentials.
- 2
Add an HTTP Request node. Point it at api.apiverve.com/v1/routinglookup using Header Auth (x-api-key). Feed in the trigger data.
- 3
Map with expressions. Add a Google Sheets node for "Add row" and reference the response with expressions such as {{ $json.data.routing_number }}.
- 4
Execute & activate. Execute manually to verify, then activate the workflow for production.
The payloadWhat Google Sheets receives.
routing_number"121000358"
office_code"O"
record_type_code"1"
new_routing_number"000000000"
bank"BANK OF AMERICA, N.A."
address"8001 VILLA PARK DRIVE"