Skip to main content
Webhooks connect Project Echo to your own systems. Use outbound webhooks to notify your endpoints when feedback activity happens, and inbound webhooks to create requests from JSON POSTs (including Tally, n8n, and Zapier). Open Integrations → Webhooks in the Workspace nav. Switch between Outbound and Inbound tabs.

​
Outbound webhooks

  1. Click Add webhook.
  2. Enter an HTTPS URL and select events (new requests, comments, votes, or published changelog entries).
  3. Save, then copy the signing secret (pe_whsec_…) — shown once.
  4. Use Send test and check the Events log.
Each delivery is a JSON POST with headers such as:
  • X-PE-Signature — HMAC-SHA256 of the raw body
  • X-PE-Event — event key
  • X-PE-Delivery-Id — delivery id
Verify signatures with the raw body and your signing secret. Internal notes do not fire comment events; votes fire on insert only. Changelog publish events fire each time an entry is published (including after an unpublish), with the title, published time, portal URL, HTML/JSON content (including image URLs), author, and linked request IDs.

​
Inbound webhooks

  1. Open the Inbound tab → Add webhook.
  2. Name the endpoint, pick a default board and status, and copy the receive URL.
  3. Send a test POST from your tool so Echo can capture a sample payload.
  4. Map email and title (required), plus optional description and name fields.
  5. Finish setup — later POSTs create requests automatically.
Mapped email resolves to a team member when it matches staff; otherwise Echo finds or creates a portal member.

​
Security tips

  • Keep signing secrets and inbound URLs private.
  • Prefer HTTPS endpoints you control.
  • Disable or delete unused webhooks.
For form/automation recipes, see Connect form and automation tools via webhooks. Help: [email protected].

Related topics

Connect form and automation tools (Tally, n8n, Zapier) via webhooksIntegrations overviewManage team roles and invitationsSecurity basics for API keys, embed tokens, and webhooksInvite your team