Plain
Create a Plain webhook target pointed at your Sazabi intake URL to stream support events into Sazabi without sharing a Plain API key.
About
Stream Plain customer support events into Sazabi by creating a webhook target in Plain yourself. You choose which event types the target subscribes to and own the target in your Plain workspace — Sazabi never receives a Plain API key on this path and does not create, edit, or delete the target.
Plain also has a Connect your account path where Sazabi provisions the webhook target for you and lets you pick event types from a Sazabi selector. See Plain account connection page for that setup.
On this path, event-type selection happens entirely in the Plain dashboard. To have Sazabi enumerate available event types and manage a consolidated webhook target for you, connect your Plain account instead.
Prerequisites
- Owner or Manager access on the Plain workspace (required to create webhook targets).
- Your Sazabi intake URL (shown above).
Set up in the dashboard
Open Plain webhooks
In your Plain workspace, go to Settings > Webhooks and click Create webhook target.
Set the webhook URL
Paste your Sazabi intake URL (shown above) into the webhook target configuration.
Select event types and enable
Enable the webhook target and select the event types you want to forward to Sazabi. Plain delivers a webhook payload for each event type you subscribe to.
Set up with the CLI
You can also register the Plain log source with the Sazabi CLI (installed and authenticated — see CLI reference).
Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):
sazabi log-sources create plain --mode connectionlessThe command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run sazabi log-sources get <log-source-id> at any time to reprint the endpoint, or sazabi log-sources list to see every log source in the project.
Verify
Save the webhook target, then trigger a subscribed event in Plain — for example create or update a thread. Open the Intake page in the Sazabi dashboard and confirm events from the Plain source appear. Events typically arrive within a few minutes of the action in Plain.
Troubleshooting
No events appear after triggering an action — Verify the webhook target is enabled in Plain and that the event type you triggered is among the subscribed types. Check the Plain webhook target's delivery log for failed POST attempts.
Events arrive but are missing expected fields — Plain's webhook payload structure varies by event type. Sazabi stores the full payload as searchable attributes, so all fields Plain sends are available in Sazabi.