Connect Google Sheets or registration data safely

Connected sources add recipient data to a certificate set. They do not replace review of the design, qualification rules or the final send. Use them when registrations arrive over time and your account includes import integrations.

Connect a Google Sheet

1. Open People → Connected sources in the intended set and choose Google Sheets.
2. Provide the supported HTTPS Google spreadsheet URL. The connector must be able to read the selected sheet's exported data; a private sheet requiring your browser login is not automatically available to the server.
3. Follow the connection instructions and consider who can access the source data before changing its sharing settings. If you cannot share the sheet appropriately, use a manual file import.
4. Preview the source and choose the correct columns for name, email, registration number, certificate type and kept data fields.
5. Choose duplicate behavior, review the sample and save the mapping before starting the initial import.
6. Run the initial sync and inspect the results in People and Import history.

Connect a registration form

The registration-data route accepts supported JSON data through a source-specific webhook. A webhook is an address your registration system sends data to; it is not a public form for attendees to fill in. Use the offered test workflow to inspect a sample before relying on live imports. Map the incoming field names explicitly.

Treat a registration webhook URL as a secret because it authorizes submissions to that source. Do not publish it in a help article, public repository or attendee instructions. Revoke the source if its access should end.

Choose a duplicate policy that fits the source

• Skip: useful when a growing list repeats people already imported.
• Update: useful when registrations are corrected, but review exactly which matching rows and fields will change.
• Error on duplicates: useful when repeated records indicate a mistake you want to resolve before importing.

Check each run

Inspect imported, updated, skipped and failed rows and the error report. A successful connection test is not proof that every later row will be valid. If headings or certificate-type values change upstream, preview and update the mapping before continuing. An imported row does not mean its certificate has been issued or emailed.

Recover from a problem

For access errors, check the sheet's export availability. For unknown fields, compare the current source headers with the saved mapping. For duplicates, inspect the chosen policy. If a run appears interrupted, inspect its history before launching another. Pause or revoke an unused source through the offered controls so a registration system cannot keep adding unintended people.