> ## Documentation Index
> Fetch the complete documentation index at: https://docs.projectecho.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect form and automation tools (Tally, n8n, Zapier) via webhooks

> Use Project Echo inbound and outbound webhooks with Tally, n8n, Zapier, and similar tools.

Project Echo does not require a separate native connector for every form or automation product. Use **webhooks** under **Integrations** to send events out and create requests from tools such as **Tally**, **n8n**, and **Zapier**.

## Create requests from a form or automation (inbound)

1. Open **Integrations → Webhooks → Inbound**.
2. **Add webhook**, set a name, and choose the default board and status for new requests.
3. Copy the receive URL into your tool:
   * **Tally** — webhook / integration that POSTs submission JSON
   * **Zapier** — Webhooks by Zapier “Custom Request” or similar action that POSTs JSON
   * **n8n** — HTTP Request node POSTing JSON to the Echo URL
4. Trigger a **test submission** so Echo stores a sample payload.
5. In Echo, map **email** and **title** (required). Map description and name fields if available.
6. Finish setup, then run a real submission and confirm the request appears.

## Push Echo activity into your automations (outbound)

1. Open **Integrations → Webhooks → Outbound**.
2. Add your n8n/Zapier/custom HTTPS catch URL.
3. Select events (for example, new member request or comment).
4. Copy the signing secret and verify `X-PE-Signature` in your workflow when possible.
5. Use **Send test**, then enable the workflow.

## Mapping tips

* Title should come from a clear form question (feature idea, bug summary, etc.).
* Use a real respondent email so ownership resolves to the right member or teammate.
* If form fields change, refresh the sample payload and update mapping.

## Troubleshooting

* **Ignored / failed inbound events** — Check the inbound Events log, required mappings, and that the body is JSON.
* **No outbound delivery** — Confirm HTTPS, selected events, and your catch URL response (2xx).

More webhook detail is in the Webhooks article. Support: [support@projectecho.io](mailto:support@projectecho.io) · [Help Center](https://docs.projectecho.io/).


## Related topics

- [Integrations overview](/integrations/integrations-overview.md)
- [Webhooks: send events out and receive requests in](/integrations/webhooks-integration.md)
- [Linear: push requests to Linear issues](/integrations/linear-integration.md)
- [Tour of the staff app (Requests, Roadmap, Changelog, Members, Settings)](/getting-started/tour-of-the-staff-app.md)
- [Security basics for API keys, embed tokens, and webhooks](/api-mcp-and-embed/security-api-keys-tokens-webhooks.md)