• INTEGRATIONS AND DEVELOPER API • SETUP GUIDE

Understanding Integration Events and Their Limitations

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

Connected integrations can receive new applications and approval events from automatic, manual admin, and API approvals in the current release.

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.

Receipt and approval are distinct events

Connected services run in the background for relevant submission and approval activity. The latest release sends approval events for manual admin, API, and automatic approvals, with each approval emitted once.

Spam is excluded, and email-marketing integrations require an applicant email. A background integration error does not invalidate the received application. Check both the app record and the external destination when investigating a missing action.

Reference and examples

Event or case Behavior
New non-spam submission Eligible connected-service activity runs in the background.
Automatic approval Approval event is emitted.
Manual admin approval Approval event is emitted.
API approval Approval event is emitted.
Same approval event App emits the approval once; external workflows should avoid duplicate work.
Spam Not forwarded to integrations.
Missing email Email-marketing action is skipped.
Background failure Application remains received; investigate the destination separately.

Example

With a test destination connected, submit a fresh non-spam application, then approve it manually. Repeat with separate applications for rule and API approval when those paths are used.

Expected result

New-submission and approval events are distinguished; approval delivery occurs once for each application decision across supported approval paths.

Limits and important behavior

  • Integrations run in the background; an integration failure does not prevent the application from being submitted.
  • Spam is not forwarded to integrations.
  • Email-marketing integrations are skipped when the submission lacks the required email.
  • Avoid assuming every external service uses identical payloads or trigger names.

Troubleshooting and verification

If submission data arrives but approval data does not, confirm the destination supports and is configured for the approval event. Manual admin, API, and automatic approvals emit that event once. Do not rely on repeating Approve as a replay mechanism.

Screenshots to add

Screenshot placeholder: Capture the app screen or test result described in “Understanding Integration Events and Their Limitations”. Include the relevant saved settings and the example outcome so readers can connect the explanation to the interface. Use dummy applicant details and mask any secrets.

Related guides