HighLevel is valuable for messaging and workflow orchestration, but it is not the system of record for event capacity, registration answers, ticket credentials, attendance evidence, or protected camper information. Connections resolve through the authorized CentriCRM location and tenant integration.

Before you beginConfirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.

Step by step

  1. Open the CentriCRM or HighLevel integration for the selected business and confirm the exact HighLevel location. Do not reuse a fixed-location token or workflow subscription across unrelated CentriPOS tenants.
  2. Before configuring a trigger or action, verify that HighLevel Marketplace registration, review, OAuth/location mapping, CentriPOS tenant entitlement, and per-location activation have actually completed. These are external controlled gates; code, documentation, or an internal schema does not prove activation, so keep the workflow disabled while any gate is pending.
  3. Only after every external activation gate is verified, create an event trigger subscription through the approved CentriPOS HighLevel workflow integration. Choose only supported event types and use an exact LeadConnector workflow trigger target generated by HighLevel.
  4. Select a privacy projection appropriate to the workflow. Normal projections remove sensitive participant fields; Sensitive projections still allow only the operational allowlist; Restricted projections fully redact business payload fields.
  5. Use offering triggers for created, updated, published, and cancelled changes; occurrence triggers for created, updated, rescheduled, cancelled, or capacity changes; registration triggers for created, updated, confirmed, cancelled, transferred, or waitlisted changes; and participant triggers for created, updated, guardian linked, or guardian updated changes.
  6. Use ticket, attendance, form, waiver, waitlist, capacity, and calendar triggers only for the workflow that genuinely needs them. Supported operational triggers include ticket issued or revoked, attendee checked in or out, registration form completed, waiver signed, waitlist offer created or accepted, threshold reached, sold out, reopened, and calendar entry lifecycle changes.
  7. Design the HighLevel workflow to deduplicate the CentriPOS event ID. Delivery can retry, and the same immutable event can legitimately arrive more than once. Preserve the event time and safe record URL for support correlation.
  8. Use only the 29 registered HighLevel actions. Registration upsert creates or updates Pending only; confirmation is a separate authoritative action. Waitlist upsert writes Waiting or Cancelled only; Offer next and Accept are separate atomic actions. Venue, ticket-preset, publication, purchase-rule, scanner, seating-layout, seating-configuration, physical-seat-hold, and event receipt payment-plan actions call bounded authoritative commands. Each action resolves tenant context from the connected HighLevel location and uses its own idempotency key.
  9. Treat action success as a CentriPOS result, not as a payment authorization or legal consent. A registration action cannot fabricate a paid receipt, bypass capacity, silently accept a waiver, or expose a meeting credential outside its authorized lifecycle.
  10. Never map medical, diagnosis, allergy, medication, emergency contact, authorized pickup, guardian authorization, waiver signature, birth date, school or student ID, social-security, password, secret, token, raw form-answer, or credential fields into general HighLevel contact custom fields.
  11. Use CentriPOS contact and participant references to prevent duplicate HighLevel contacts. A guardian may be an appropriate CRM contact; a camper may remain only a protected CentriPOS participant unless the business has a lawful, explicit reason and approved workflow for a separate CRM record.
  12. Monitor subscription status, delivery attempts, retries, and dead letters. CentriPOS uses bounded exponential retries and stops after the supported attempt limit; correct the receiver before replaying.
  13. Test each trigger and action in an isolated preview context with synthetic records. Verify wrong-location rejection, missing-scope rejection, sensitive-field stripping, idempotent retry, capacity enforcement, status transitions, and audit correlation before enabling customer communications.
  14. The exact 96-trigger vocabulary is event.created, event.updated, event.published, event.cancelled; event_occurrence.created, event_occurrence.updated, event_occurrence.rescheduled, event_occurrence.cancelled, event_occurrence.capacity_changed; registration.created, registration.updated, registration.confirmed, registration.cancelled, registration.transferred, registration.waitlisted; participant.created, participant.updated, participant.guardian_linked, participant.guardian_updated; waitlist.offer_created, waitlist.offer_accepted; ticket.issued, ticket.updated, ticket.revoked; attendee.checked_in, attendee.checked_out; registration_form.completed; waiver.signed; capacity.threshold_reached, capacity.sold_out, capacity.reopened; calendar.entry.created, calendar.entry.updated, calendar.entry.cancelled; venue.created, venue.updated, venue.archived; ticket_preset.created, ticket_preset.updated, ticket_preset.archived; purchase_rule.created, purchase_rule.updated, purchase_rule.archived; scanner.device_registered, scanner.device_updated, scanner.device_retired, scanner.batch_synchronized; ticket.delivery_configuration.updated; ticket.artifact_ready, ticket.artifact_failed, ticket.artifact_revoked, ticket.artifact_updated; seating.layout.created, seating.layout.updated, seating.layout.published, seating.layout.archived; seating.configuration.created, seating.configuration.updated, seating.configuration.on_sale, seating.configuration.archived; seating.hold.created, seating.hold.updated, seating.hold.released, seating.hold.expired, seating.hold.converted; seating.assignment.created, seating.assignment.updated, seating.assignment.released, seating.assignment.transferred; seating.seat.blocked, seating.seat.unblocked; access_code_set.created, access_code_set.updated, access_code_set.archived; access_code.created, access_code.updated, access_code.revoked; access_code.reservation_created, access_code.reservation_updated, access_code.reservation_confirmed, access_code.reservation_expired, access_code.reservation_released; seating.intent_seat_held, seating.intent_seat_updated, seating.intent_seat_assigned, seating.intent_seat_released; event_payment_plan_policy.created, event_payment_plan_policy.updated, event_payment_plan_policy.archived; event_registration_payment_plan.activated, event_registration_payment_plan.paused, event_registration_payment_plan.resumed, event_registration_payment_plan.delinquent, event_registration_payment_plan.completed, event_registration_payment_plan.canceled, and event_registration_payment_plan.admission_reinstated.
  15. The exact 29 action keys are centripos_event_upsert, centripos_occurrence_upsert, centripos_registration_upsert, centripos_registration_confirm, centripos_participant_upsert, centripos_guardian_link_upsert, centripos_registration_cancel_or_transfer, centripos_waitlist_upsert, centripos_waitlist_offer_next, centripos_waitlist_accept, centripos_ticket_issue_or_revoke, centripos_attendance_record, centripos_calendar_entry_upsert, centripos_venue_upsert, centripos_ticket_preset_upsert, centripos_event_validate_or_publish, centripos_purchase_rules_save, centripos_scanner_device_register, centripos_seating_layout_publish, centripos_seating_configuration_upsert, centripos_seat_hold, centripos_seat_hold_release, centripos_seat_hold_confirm, centripos_receipt_payment_plan_create, centripos_receipt_payment_plan_pause, centripos_receipt_payment_plan_resume, centripos_receipt_payment_plan_cancel, centripos_receipt_payment_plan_send_customer_link, and centripos_receipt_payment_plan_reinstate_admission. Payment-plan lifecycle actions call the receipt/invoice plan authority; there is no mark-paid action. Do not substitute a generic table update for an authoritative lifecycle command.
  16. Venue, ticket-preset, purchase-rule, scanner, ticket-delivery, artifact, seating, access-code, reservation, and registration-intent seat triggers use the same tenant resolution, immutable event identity, delivery retry, privacy projection, and branded record-link rules as the original event vocabulary. HighLevel access-code triggers include lifecycle metadata only; raw codes, code_hash, and even the masked hint remain outside the CRM payload boundary.
  17. The new HighLevel actions remain deliberately narrower than the Retail API. centripos_event_validate_or_publish validates or publishes through the database lifecycle; centripos_purchase_rules_save replaces one bounded rule graph; centripos_seating_layout_publish and centripos_seating_configuration_upsert preserve layout/configuration state; and centripos_seat_hold, centripos_seat_hold_release, and centripos_seat_hold_confirm use authoritative seat-inventory commands. There is intentionally no HighLevel action that transports or creates a raw access code.
  18. Event payment-plan workflow triggers carry the same safe lifecycle projection as signed delivery and never carry card, vault, payment-link, medical, waiver, or answer data. centripos_receipt_payment_plan_create creates the event receipt plan through the existing invoice-plan authority; pause, resume, and cancel call the existing receipt-plan lifecycle. send_customer_link returns the actual canonical expires_at: its requested lifetime applies only when a new receipt token is created, and a reused live token keeps its existing expiry. Its scheduled amount is only a prefill on the ordinary receipt page, where the customer may pay that amount, the full balance, or another valid partial amount. centripos_receipt_payment_plan_reinstate_admission requires payment_plan_id and a 1–1000 character reason, requires the authoritative completed receipt balance to be zero, atomically rechecks live registration, daypart/session, and physical-seat capacity, and returns safe registrations_reinstated, occurrence_enrollments_reinstated, seats_reinstated, and tickets_issued counts. No HighLevel action marks an installment or receipt paid.
  19. An outbound trigger target is accepted only at https://services.leadconnectorhq.com/workflows-marketplace/triggers/execute/{trigger}/{location} with no user info, port, query, or fragment. A subscription may define at most 32 normalized filters against the already-projected payload; each filter list has at most 100 scalar values, so filtering cannot recover a redacted field.
  20. Each encoded HighLevel workflow payload is capped at 256 KiB. Delivery makes at most eight total attempts, starts with a 30-second exponential delay capped at six hours, and retries only network failures, 408, 409, 425, 429, or 5xx responses. Delivered, dead-lettered, and suppressed are terminal; reuse the immutable event ID and subscription identity for deduplication.
  21. HighLevel Marketplace registration, action/trigger definition publication, OAuth/location mapping, reviewer approval, and customer-workflow activation remain external controlled gates. Keep production workflows disabled until that app is approved and the target CentriPOS tenant is entitled; never interpret deployed code or documentation as Marketplace activation.

Screen and contract reference

Control or areaWhat it means
HighLevel locationExternal account context mapped to exactly one authorized CentriPOS tenant integration.
Manual marketplace activationPlatform-controlled publication of CentriPOS trigger and action definitions in HighLevel; not implied by application code.
Tenant entitlementExplicit CentriPOS authorization for this business to use the event workflow contract; documentation alone is not entitlement.
Trigger subscriptionApproved event-type and LeadConnector workflow target relationship.
Privacy projectionNormal, sensitive allowlist, or fully restricted outbound field boundary.
Immutable event IDDeduplication key that remains the same across delivery retries.
Record URLBranded safe link or API resource reference used for correlation.
Offering/occurrence triggerWorkflow event about program content or schedule state.
Registration triggerWorkflow event about enrollment lifecycle.
Capacity triggerThreshold, sold-out, reopened, or capacity-change signal.
CentriPOS actionHighLevel-initiated upsert or lifecycle command validated by the tenant system of record.
Idempotency keyCaller-supplied retry identity preventing duplicate action writes.
Sensitive-field strippingRemoval of child, medical, emergency, waiver, credential, and secret data before delivery.
event.created · event.updated · event.published · event.cancelledOffering lifecycle triggers available to HighLevel workflows.
event_occurrence.created · event_occurrence.updated · event_occurrence.rescheduled · event_occurrence.cancelledOccurrence lifecycle triggers available to HighLevel workflows.
event_occurrence.capacity_changedOccurrence capacity-change trigger.
registration.created · registration.updated · registration.confirmedRegistration creation, general update, and confirmation triggers.
registration.cancelled · registration.transferred · registration.waitlistedRegistration cancellation, transfer, and waitlist triggers.
participant.created · participant.updatedParticipant lifecycle triggers with protected-field projection.
participant.guardian_linked · participant.guardian_updatedExplicit guardian relationship and portal-authorization lifecycle triggers.
waitlist.offer_created · waitlist.offer_acceptedWaitlist offer lifecycle triggers.
ticket.issued · ticket.updated · ticket.revokedTicket credential lifecycle triggers without delivering credential secrets.
attendee.checked_in · attendee.checked_outAttendance triggers from accepted operational evidence.
registration_form.completed · waiver.signedCompletion signals; payload privacy still strips protected answers and signatures.
capacity.threshold_reached · capacity.sold_out · capacity.reopenedCapacity automation triggers.
calendar.entry.created · calendar.entry.updated · calendar.entry.cancelledMaster calendar lifecycle triggers.
centripos_event_upsertHighLevel action that creates or updates a CentriPOS offering.
centripos_occurrence_upsertHighLevel action that creates or updates an occurrence.
centripos_participant_upsertHighLevel action that creates or updates an event participant under the native privacy boundary.
centripos_guardian_link_upsertHighLevel action that explicitly links or updates a Parent/Guardian relationship and portal authorization.
centripos_registration_upsertCreates or updates only a Pending registration; it cannot confirm, cancel, transfer, or fabricate payment.
centripos_registration_cancel_or_transferHighLevel action for an authorized cancellation or transfer.
centripos_waitlist_upsertCreates or updates only Waiting or Cancelled queue state; offer and acceptance are separate commands.
centripos_ticket_issue_or_revokeHighLevel action that issues or revokes a ticket under CentriPOS rules.
centripos_attendance_recordHighLevel action that appends check-in, check-out, or correction evidence.
centripos_calendar_entry_upsertHighLevel action that creates or updates a canonical calendar entry.
Dead letterDelivery stopped after the supported retry limit and requiring review.
Marketplace gateExternal registration, review, approval, and per-location activation required before customer workflows may use these contracts.
Authoritative actionTenant-resolved idempotent lifecycle command; never an unrestricted direct-table mutation.
HighLevel delivery boundary256 KiB projected payload, eight total attempts, and a fixed LeadConnector marketplace-trigger target shape.
Workflow filterOne of at most 32 conditions applied only after privacy projection; it cannot address fields that CentriPOS removed.
centripos_registration_confirmConfirms a Pending registration through confirm_event_registration; it is separate from pending-only upsert.
centripos_waitlist_offer_nextAtomically offers the next capacity-eligible Waiting entry through offer_next_event_waitlist_entry_from_workflow.
centripos_waitlist_acceptAccepts one active offer through accept_event_waitlist_offer_from_workflow and returns its registration lifecycle result.
centripos_venue_upsert / centripos_ticket_preset_upsertBounded idempotent configuration upserts through the event-platform workflow command.
centripos_event_validate_or_publishRuns publish validation or the authoritative publication transition; it cannot bypass blocking issues.
centripos_purchase_rules_saveReplaces one bounded visual purchase-rule graph and leaves checkout authorization to server evaluation.
centripos_scanner_device_registerRegisters one tenant scanner device through the authoritative device command.
centripos_seating_layout_publish / centripos_seating_configuration_upsertPublishes a valid reusable layout or upserts one occurrence seating configuration.
centripos_seat_hold / release / confirmCreates, releases, or converts physical-seat holds through the server inventory lifecycle; the hold key input is a digest, never a raw session secret.
Access-code workflow boundaryHighLevel triggers expose safe lifecycle metadata without raw code, code_hash, or code_hint. No HighLevel action creates an access code.
Event receipt payment-plan actionsCreate, pause, resume, cancel, generate a customer link, or reinstate paid-in-full admission through the existing receipt/invoice-plan authority; no mark-paid shortcut exists.
centripos_receipt_payment_plan_reinstate_admissionRequires payment_plan_id plus a nonblank 1–1000 character reason; current receipt balance must be zero, live capacity is rechecked, and safe restored-registration and ticket counts are returned.

Expected result

Each enabled HighLevel trigger arrives once logically despite retries with the correct tenant and privacy projection, and every supported action is tenant-resolved, scope-checked, idempotent, capacity-safe, lifecycle-valid, and auditable in CentriPOS.

Troubleshooting

  • Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.
  • Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.
  • Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.