OPVII

Available Connectors

The seven routes registrations can take into your workspace, and what each one is for. It sits under Connectors & Integrations in the knowledge base. Related guides are listed at the end, and the whole library is searchable from the index. If this does not answer your question, our team picks it up from the contact page.

Searchable Library Updated In Place Humans On The End

Browse The Library

Every guide, grouped by topic, with a count on each one.

Search Every Article

Titles, categories and article bodies, filtered as you type.

Ask Our Team

A person answers, usually inside one business day.

Connectors & Integrations

Available Connectors

The seven routes registrations can take into your workspace, and what each one is for.

Last updated October 22, 2026

Use this to pick the right route for a registration source you already have. There are seven, they can all be used at once, and every one of them lands in the same place and starts the same reminder flow.

The Seven Routes In

1. Forwarded Email

You add a rule in your own mail program that forwards registration confirmations to a private address OPVII gives you. Works with any mail host, needs no sign-in, and is the default. See Connecting Your Email Inbox.

2. Gmail

Either forwarding with a Gmail filter, or IMAP with a Google App Password. There is no Google sign-in button for mail: OPVII does not connect Gmail over OAuth.

3. Microsoft 365 Or Outlook

Business accounts sign in once with their normal Outlook account and OPVII reads confirmations straight out of the inbox. Personal Outlook.com accounts can forward or use IMAP instead.

4. Any IMAP Mailbox

OPVII logs in to the mailbox on a schedule and pulls matching messages. Covers iCloud, Yahoo, Zoho, GoDaddy, cPanel, Plesk, DirectAdmin, SmarterMail and anything else that speaks IMAP.

5. The Web Signup Form

A hosted registration form, found on the Connections page under the Web Form tab as Web Signup Form. Three things sit there:

  • Share The Link. Click Copy Link and email it, text it or print it.
  • Put It On Your Site. Click Copy Code for an embed snippet that fits whatever space you give it.
  • Registration QR Code. Click Download PNG to print it on flyers or show it on screen.

The form lets the registrant pick which of your upcoming events they want. Submissions become registrations exactly like a forwarded email.

6. CSV Import

A one-time upload for a list you already hold. On the Connections page, open the Import & API tab and click Import CSV, or go straight to the page titled Import A Spreadsheet.

Your file needs a header row. Column names are matched without regard to case. The columns OPVII reads are:

  • email, which is required
  • first_name
  • last_name
  • phone
  • event_title
  • event_date

Limits are 5 MB and 2,000 rows. Rows with neither an email address nor a phone number are skipped and reported back to you row by row. Events are matched by title and date, or created if new. Click Download Sample CSV for a file in the right shape, then Import Registrations.

7. The REST API

For your own software. On the Connections page, open the Import & API tab, then API Keys, and create a key. Requests carry it as a bearer token. POST /api/v1/registrations creates the contact and the registration and enrolls them into your trigger flow in one call. There are also endpoints for contacts, events, attendance, flows and a read-only message log. Full reference is at /developers.

What OPVII Does Not Have

Said plainly, because these come up and the answer is no:

  • No Google Forms connector. There is no Google Forms path of any kind. Use the web signup form, or have the form email you and forward that.
  • No Zapier or Make connector. Use the REST API.
  • No Typeform, Jotform, Gravity Forms or Eventbrite connector. If the service emails you a confirmation, forward it or match it with an IMAP rule, which is how most of these are handled in practice.
  • Webhooks do not bring registrations in. This one is worth being clear about, because the name points the wrong way.

Webhooks Go Out, Not In

The Webhooks feature sends signed event notifications from OPVII to a URL you own. It is a way to tell your systems what happened here, not a way to push registrations to OPVII. The events you can subscribe to are registration.created, registration.cancelled, registration.moved, attendee.replied and message.sent.

To create registrations from your own software, use the REST API instead.

How To Tell A Connector Is Working

Open the Arrivals tab on the Connections page. Everything that has come in is listed with what became of it, filterable by All, Imported, Nothing Found, Filed In Inbox and Turned Away. CSV and API imports confirm themselves: the CSV page reports how many rows were imported and how many skipped, and the API returns the created records.

If Something Goes Wrong

The CSV Imported Fewer Rows Than Expected

Rows with no email address and no phone number are skipped, each with its own message naming the row number. If the file was over 2,000 rows you will see Import stopped at the 2000-row limit. Split the file and re-upload the rest.

The Web Form Shows No Events

It only lists upcoming, scheduled events. Create one with a future date, or check that your existing events have not all been called off or already happened.

An API Call Returns 403

The key resolved but lacks the scope for that endpoint. Open API Keys and widen the key's scopes, or create a key for the job.

Where To Go Next