Support email
Email support@fasthook.io for product questions, account access, billing context, privacy requests, security reports, or documentation corrections.
Choose a clear subject
A specific subject helps route the message without requiring you to include private data. Useful prefixes are Product support, Account access, Billing, Privacy, Security, and Documentation correction. Include the workspace or resource name only when it is safe to share; a FastHook request or event identifier is usually more useful than copying a complete webhook payload into email.
What to include
- The FastHook feature or documentation page involved.
- A request, event, or attempt identifier when reporting delivery behavior.
- The approximate time and timezone of the issue.
- Redacted logs or screenshots that show the problem without exposing secrets.
Protect sensitive data
Do not email API keys, signing secrets, OAuth tokens, passwords, or unredacted webhook payloads. Replace credentials and personal data with safe placeholders before sending diagnostic material.
Product and delivery troubleshooting
For an ingress problem, identify the source, HTTP method, approximate request time, and the status shown in the Requests view. For a downstream problem, include the connection, destination, event identifier, latest attempt status, and whether a manual retry behaves differently. Describe the expected result separately from the result you observed. This lets support follow the same request-to-event path without asking for credentials.
If the issue is intermittent, note its frequency and the earliest and latest known occurrence. Response bodies and headers can be useful after they are redacted. Screenshots should hide tokens, email addresses, customer records, and any URL containing a secret. Keep the original evidence in your own secure system in case a more targeted excerpt is needed later.
Account, billing, and privacy requests
Account-access messages should be sent from the address associated with the account when possible and should name the affected workspace. Billing questions should include the invoice date or a non-sensitive invoice identifier, never full payment-card details. Privacy requests should describe the action requested and the data or account concerned so identity and scope can be verified before any irreversible change is made.
Security reports
Use the subject Security report and provide concise reproduction steps, the affected FastHook surface, potential impact, and a safe way to confirm the behavior. Do not test against data or workspaces you do not own, disrupt service, or publish exploitable details before the report can be reviewed. Acknowledgement and resolution timing depend on severity, reproducibility, and the information available; this contact page does not create a separate service-level agreement or bug-bounty commitment.
What happens after you write
The message is reviewed for ownership, scope, and the minimum evidence needed to investigate it. FastHook may ask for a narrower reproduction, a sanitized identifier, or confirmation from the account owner. Requests that depend on a third-party provider can also require checking that provider's current status, permissions, or API response before a FastHook change is appropriate.
Privacy and content corrections
The Privacy Policy explains data handling and user choices. For an inaccurate or outdated technical claim, send the page URL, the affected passage, and a source or reproduction that demonstrates the correction. Our update process is described in the Editorial Policy.