Upload receipts using Zapier

You can now automatically upload receipts from your Gmail inbox to your Bokio company account using this prebuilt Zapier template. This automation streamlines your bookkeeping by sending attachments directly to Bokio without manual upload.

💡 Gmail is just one example. You can use this setup as inspiration for other sources — like Google Drive, Dropbox, or anywhere else you receive receipts or invoices.

What This Template Does

This Zapier template includes the following preconfigured steps:

• Trigger: Watches for new emails in Gmail.
• Filter: Checks that the email contains attachments.
• Action: Sends the attachment to Bokio via a Webhook.

What You Need to Do

Only one step requires your input, and it’s in the last step (Webhook by Zapier).

Add Your Bokio Company ID

To ensure the file uploads to the correct Bokio company, you need to replace the companyId placeholder in the URL field in the Webhook step with your actual Company ID. Follow these steps to find the companyId:

1. Log in to your Bokio account.
2. Navigate to the correct company (if you have multiple).
3. Look at the address bar in your browser, the Company ID is part of the URL. Example: https://app.bokio.se/**123456**/dashboard — here, 123456 is your Company ID.

Add Your Bokio API Token

The API token gives secure access to your Bokio company. To insert your token in the Headers field, replace the token placeholder with your actual API token. Here's how to find it:

1. Log in to Bokio.
2. Select the correct company (if applicable).
3. Go to Settings > API Tokens.
4. Click Create Token (if you haven’t created one yet).
5. Click Copy to copy the token to your clipboard.

✅ Make sure to keep this token secure — it grants access to your Bokio data.

You’re all set! Now go ahead and run your Zap to test the integration.

Customize This Flow Further

Although this template uses Gmail, the same setup can work with:

📁 Google Drive (New file in folder)

☁️ Dropbox (New file upload)

💬 Slack, 📸 receipt scanners, 📝 form uploads, etc.

Just change the trigger, and keep the rest of the logic.

Security Tips

• Keep your API Token and Company ID private.
• Do not share screenshots or Zap links with those fields exposed.
• Rotate your token periodically if you're using it long-term.