What to include
The more of this you send in the first message, the less back and forth there is.- Organisation name and, if you have it, your organisation reference from the Support page.
- Workspace you were working in, if your organisation has more than one.
- Package or template id (
pkg_...ortmpl_...). Ids are in the address bar on the package or template page, and in every API response. - What you expected and what happened, with the time it happened. Timestamps let us find the matching log lines.
- Screenshots of any error message, cropped to the part that matters.
For API and webhook issues
- The request method and path, for example
PATCH /api/v1/packages/pkg_9f3c2e. - The HTTP status code and the full error body (
{ "error": ..., "details": ... }). - The key’s name or prefix, never the key itself. Redact
Authorizationheaders and webhook secrets from anything you paste. - For webhooks, the
x-flowsign-delivery-idof the delivery in question and your endpoint’s response status.
Something else?
- Security vulnerabilities go to a different address. See Report a problem.
- Privacy requests are covered on the Privacy page.
- Pricing and plans are on flowsign.app/pricing.

