Integrations and source ownership

• Streaming and event delivery platform. Live video, breakout rooms, networking, polls and chat run here. Send join events back to record admitted times.
• Registration website. Send registrations with a stable attendee reference and quantity.
• Payment provider. Send authorizations, captures, refunds and voids into payment evidence with the provider’s event ID and reference.
• Email and calendar. Send confirmations, join links, schedule changes and cancellation notices.
• Accounting software. Export verified ticket payments and refunds for bookkeeping.
• Identity provider. Map staff sign-in to team members; removing a leaver’s access must also remove their platform access.

Each connection needs an agreed source of truth, a field mapping, a stable event identifier and a retry policy. A repeated payment notification must not create a second piece of evidence, and a repeated join must not admit an attendee twice. Keep credentials in the approved secret store and grant the smallest scope the connection needs. Queue rejected records with their source identifier and a visible reason.

Test a provider timeout, a duplicate notification and a revoked credential before turning on schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree acceptance criteria for each connection.