Connect Firebase Auth to Customer Spine
Sign-ups and sign-ins, so a profile exists from the moment someone creates an account.
Where the data goes
Every teamspace gets one endpoint for all sources — the signature header each vendor sends tells us which integration delivered the event. You are given the real one when you sign in — the last segment is your teamspace id.
https://ingest.customerspine.com/ingest/<your-teamspace-id>Method POST · Header X-Ingest-Signature
How it authenticates
You forward events from a blocking function or an export, signing the body with the generated secret.
Steps
- 1Add a blocking functionUse a beforeUserCreated or beforeUserSignedIn blocking function, or a scheduled export of the Auth user list.
- 2POST the user recordSend the Firebase user record as JSON to the URL above.
- 3Sign the bodySet X-Ingest-Signature to the hex HMAC-SHA256 of the exact request body, keyed with the generated secret. If you wrap the user record in your own envelope rather than sending it as-is, also set X-Ingest-Source: firebase so the source is recognised.
Worth knowing
An unverified email address is recorded as a trait but never used to merge profiles. Unverified addresses are user-typed, and merging on one is how two different people become a single customer.