SharpSpring Source Configuration

SharpSpring configuration

Create a SharpSpring source, keep POST enabled, and provide the configured Webhook URL Secret values for provider signature. FastHook uses these settings to validate each SharpSpring delivery before it enters the routing workflow.

{
  "type": "SHARPSPRING",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "SHARPSPRING",
      "webhook_signing_secret": "long-random-url-secret",
      "query_parameter_name": "secret"
    },
    "allowed_http_methods": ["POST"]
  }
}

SharpSpring request contract

FastHook checks a secret query parameter and removes it from stored request metadata before storing the postback.

SharpSpring headers

Preserve the source authentication values when sending SharpSpring test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

The SharpSpring source does not require provider-specific signature headers. Use its configured source auth fields and inspect rejected requests if SharpSpring does not match the saved credentials.

SharpSpring setup

1. Create a SharpSpring source and choose a long random Webhook URL Secret.
2. Append ?secret=YOUR_SECRET to the Source URL and use that full value as the form Postback URL.
3. Submit a test lead and confirm the received field names before mapping downstream systems.
4. Keep the URL secret private because SharpSpring does not publish a standard payload signature for form postbacks.

Continue with SharpSpring

• SharpSpring help center
• Source operations and troubleshooting