Overview
A complete test has two stages.
Stage 1 proves that PulseGrid can reach the endpoint.
Stage 2 proves that a normal channel event automatically creates a webhook delivery.
The project selected on the Webhooks page must be the same project that owns the channel. If the endpoint belongs to Alpha and the message is published in Yinhla101, no delivery should be created. That is correct project isolation, not an error.
Setup
Stage 1 - connection test:
1. Create the Webhook.site endpoint with Events set to *.
2. Click Send test.
3. Confirm Webhook.site receives event pulsegrid.test.
4. Confirm PulseGrid Recent activity shows Succeeded and HTTP 200.
Stage 2 - real event test:
1. Note the project selected on the Webhooks page, for example Alpha.
2. Open Channels.
3. Select Alpha, not a different project.
4. Open an Alpha channel console.
5. Enter only: Hello from Alpha
6. Click Send message.
7. Return to Webhook.site.
8. Confirm a second POST request arrived with event message and source websocket.
9. Confirm the project object says Alpha.
The Channel Console message box expects normal message text. Do not paste a complete JSON envelope into that box. PulseGrid automatically supplies project, channel, sender, event, metadata, source, IDs and timestamp.
Code example
Type this in the Channel Console:
Hello from Alpha
Expected data section:
{
"data": {
"text": "Hello from Alpha"
},
"event": "message",
"source": "websocket"
}Notes
If you paste JSON into the normal Message box, PulseGrid treats that entire JSON document as message text. The resulting payload will contain the JSON string inside data.text. That is valid transport behaviour, but it is not the clean console test.
After one test delivery and one real message, the dashboard normally shows two deliveries, two successes, and two HTTP attempts when both succeeded on their first attempt.