Automation · Native
LinkedCamp × Webhooks
Fire HTTP POSTs on any LinkedCamp event.
How LinkedCamp and Webhooks work together
Every LinkedCamp event — connection accepted, message sent, reply received, meeting booked — can fire a webhook POST to your URL of choice. Payloads are JSON with HMAC-SHA256 signatures for verification. The simplest way to wire LinkedCamp into custom internal tools.
What you can do with it
Setup
- 1LinkedCamp → Settings → Webhooks → Add endpoint
- 2Paste your HTTPS URL
- 3Select which events to subscribe to
- 4Verify payloads using the signing secret (HMAC-SHA256 of body)
Frequently asked about LinkedCamp × Webhooks
What events can I trigger from Webhooks?+
LinkedCamp exposes ~15 events: connection-accepted, message-sent, reply-received, meeting-booked, campaign-completed, profile-viewed, and more. All are available as native triggers.
Can I trigger LinkedCamp actions from Webhooks?+
Yes. Start/pause campaigns, enroll contacts, send messages, and update contact fields via actions exposed in the Webhooks connector. Every write-action authenticates via your LinkedCamp API token.
Are webhook payloads signed?+
Yes — all webhooks include an X-Signature header with an HMAC-SHA256 signature of the payload body. The signing secret is shown once in Settings → Webhooks. We retry failures with exponential backoff for up to 24 hours.
How is this different from using the LinkedCamp REST API directly?+
Webhooks gives you a no-code layer for the common cases (new reply → Slack DM, booked meeting → Google Sheet). Use the REST API directly when you need batch operations, custom data shapes, or tighter latency than Webhooks's polling/trigger model.
What plans include the Webhooks integration?+
The Webhooks integration is available on Turbo / Pro / Agency plans. It's part of every LinkedCamp plan — even the $69/mo Turbo tier.
Try LinkedCamp × Webhooks
14-day free trial, dedicated IP, AI agents — and native Webhooks integration from day one.
