Skip to content
EntryWick documentation

Zapier — EntryWick for Zapier · integrations/zapier

Connect EntryWick to thousands of apps without code: add a row to a Google Sheet for every check-in, create a registration from a form tool, look a registration up before sending a message. Built in week 15 step 4 on API v1 and webhooks alone (ADR-009, ADR-027).

Who can use it

  • Growth and above can connect it (zapier). On Growth: every trigger, and Find Registration.
  • Scale and above also get the actions: Create Registration, Add Attendee, Issue Ticket, Record Check-in. On Growth they answer "This action needs the Scale plan".

Connecting

  1. In EntryWick, Organization → API keys → New key. Scopes: read and write; add scanner if a Zap records check-ins. A key limited to a group only hears about, and only changes, that part of the organization. Use a Test key to try things out: its check-ins stay out of every live count.
  2. In Zapier, pick EntryWick and paste the key. The connection is labelled with the organization and key name.

Triggers

New Registration · Registration Confirmed · Registration Cancelled · Ticket Issued · New Check-in (every recorded scan, refused ones included; its result says what happened) · Payment Received. Each can be limited to one event.

Turning a Zap on makes a webhook endpoint in Organization → Webhooks described "Zapier: …"; turning it off deletes it. Leave those endpoints alone: deleting one stops its Zap, and rotating its secret stops the Zap after the 24-hour overlap (Zapier checks each delivery's signature) until the Zap is turned off and on again.

Fields arrive flat: nested values are parent__child (submitted_by__email), a registration also has attendee_count and attendee_names, and every item has envelope_id, event_type, occurred_at and livemode.

Actions and search

  • Create Registration — one person, through the event's own rules, capacity and approval. Status left empty lets the event decide; Confirmed skips approval and payment.
  • Issue Ticket — for a person (and day) that has none.
  • Record Check-in — the same decision the scanner makes; a refused scan is a result, not an error.
  • Find Registration — by name, email, phone or ticket, or your own external id.

Add Attendee puts one more person on a registration that already exists (a registration id from New Registration, Create Registration or Find Registration), placed by the event's own rules and capacity; on a confirmed registration their tickets are issued at once.

Not yet: voiding tickets.

Audit

Every change made through Zapier is in the organization's audit log with source api, the key as actor and client zapier.

Open

  • Owner: Zapier developer account, zapier register / push, listing and review submission (NEEDS_FROM_OWNER.md).
  • Staging gate: a Zap "New Check-in → Google Sheets row" firing within seconds.