• INTEGRATIONS AND DEVELOPER API • SETUP GUIDE

How to Connect the Official Zapier App

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Connect the official Rivio Zapier app with a Developer API key to automate Shopify wholesale application workflows.

Before you begin

Use the intended service account and select the destination list, channel, spreadsheet tab, or endpoint. Decide whether you are testing a new-submission event or an approval event, and use a clearly identifiable test application.

Triggers and actions need different permissions

The official integration has New Wholesale Application and Application Approved triggers, plus Approve Application, Reject Application, and Find Application by ID actions. Connect using the base URL and Developer API key required by its current authentication fields.

Read permission fits lookup and polling. Add status-update permission only when the Zap needs a decision action. The retired Catch Hook workflow is not the documented setup; use the official app and test with a known disposable application.

Set up this workflow

  1. Open Integrations and locate the Developer API key-management page.

  2. Create a read key for polling triggers, adding update-status permission only if the Zap requires approval or rejection actions.

  3. In Zapier, select the official app and connect it using the base URL and full API key shown by the current app documentation.

  4. Choose New Wholesale Application or Application Approved as the relevant trigger.

  5. Configure Approve Application, Reject Application, or Find Application by ID only when those actions fit the workflow.

  6. Test with a known application and inspect the resulting status and integration activity.

Example

Build a test Zap with New Wholesale Application and a simple destination you control. Use a read-permission key unless the Zap needs a status update.

Expected result

A new test application triggers the Zap; approval/rejection actions are configured and tested separately with the needed permission.

Limits and important behavior

  • Use the app’s public base URL, not the Shopify store domain, where the connector asks for the Developer API base URL.
  • The previous Catch Hook option was removed; use the official app.
  • Each key is limited to 60 requests per 60 seconds, including Zapier polling and actions.

Troubleshooting and verification

If Zapier cannot find or update an application, verify the current API key, read/write scope, selected trigger or action, and application ID. Use the official Rivio app. The removed Catch Hook setup should not be substituted for the documented connection.

Screenshots to add

Screenshot placeholder: Capture the relevant app screen for “How to Connect the Official Zapier App” after completing the setup. Show the controls used to open Integrations and locate the Developer API key-management page. Add a second screenshot showing the result of this check: Test with a known application and inspect the resulting status and integration activity. Use dummy applicant details and mask any secrets.

Related guides