A report should identify the listing or content involved and explain the concern clearly enough to review. Reporting is distinct from asking how to configure a remix or resolve an application error.
Prepare a useful report
Include:
- The listing link and relevant version when known.
- What you observed and where it appears.
- Why it appears misleading, unsafe, unauthorized, or otherwise problematic.
- A concise example or screenshot that supports the concern.
Keep evidence proportionate. Do not include credentials, unrelated private conversations, or customer data that is unnecessary to explain the issue.
Choose the appropriate channel
Use the report action where the content surface provides one. If no report action is available, contact Playbooks support with the listing link and the same focused evidence. This documentation does not promise a particular report interface on every listing surface.
For a setup problem, first review the template's requirements and Remixing. For an issue with your own resource, Logs can help establish what failed.
Understand the outcome
Submitting a concern does not itself withdraw a listing, reverse a completed external action, or remove independent remixes. Do not assume a report has changed the content's availability until the relevant state or response confirms it.
If you publish the affected material, review whether to correct the listing, publish a new version, or withdraw it through your authorized controls.
Example: report a misleading claim
If a listing claims to include an integration that its package does not provide, include the listing URL, selected version, exact claim, and the observed setup gap. A concise screenshot or excerpt can establish the discrepancy without exposing private account data.
For an expired connection in your own remix, use the Connection troubleshooting guide instead of treating it as evidence that the listing itself is misleading.
Keep the concern specific
Distinguish an inaccurate listing claim from a failed operation in your own setup. For example, “Version 2 lists a report template that is absent from the reviewed package” identifies something to inspect. “The integration does not work” needs the operation, error, and setup context before its cause is clear.