Skip to main content
Peoplewisher is designed to be the celebration engine, not another application your users have to operate. Your integration should primarily move people data into Peoplewisher and assign each person to the right Celebration Group.

​
Your application

Your application is responsible for:
  • identifying the people who should be celebrated
  • maintaining your own customer and tenant records
  • deciding which Peoplewisher group a person belongs to
  • creating and updating Peoplewisher contacts
  • removing contacts when they should no longer be managed by PeopleWisher

​
PeopleWisher

Peoplewisher is responsible for:
  • celebration workflow execution
  • templates
  • channel configuration
  • message timing
  • celebration settings
  • email delivery
  • SMS delivery
  • WhatsApp delivery
  • delivery history and reporting

​
Why groups matter

A Celebration Group is the bridge between your data and a Peoplewisher workflow. For example:
The exact behavior is configured in PeopleWisher.

​
Multi-tenant SaaS

A multi-tenant SaaS product can use Peoplewisher without exposing PeopleWisher’s internal workflow configuration to its own users. Maintain a mapping such as:
Then your synchronization process only needs to:
  1. identify the tenant
  2. resolve its Peoplewisher group
  3. create or update the contact
  4. assign the contact to that group
If tenants require separate Peoplewisher accounts, keep a separate API key and account mapping for each account.

​
What is intentionally not in the API

The public API does not currently expose operations for:
  • creating templates
  • updating template content
  • configuring channel automation
  • changing celebration timing
  • changing group celebration settings
  • triggering arbitrary message content
Those operations stay inside Peoplewisher so that the platform remains the central place where celebration behavior is managed.