Contact Postifys
Use one public email for product questions, privacy or deletion requests, and security reports. Include enough context for a useful reply, and never send live API keys or customer tokens.
Email support@postifys.comReviewed: 23 July 2026
support@postifys.com
This address is also listed on our Privacy Policy and Terms. For security reports, start the subject with “Security report” and include reproduction steps.
Common contact reasons
Product help
Account access, publishing setup, n8n node questions, or API onboarding.
Privacy
Access, correction, or deletion requests related to your Postifys account.
Security
Suspected vulnerabilities or unauthorized access concerns.
Teams / agencies
Questions about seat sizing and multi-account workflows.
Before contacting support about a failed post, check Post History for the platform error message and confirm the connected account still has the required permissions.
Resources that answer most setup questions
Many publishing, OAuth, and n8n workflow questions are documented publicly. Checking these pages first usually saves a round trip and gives your team copy-paste examples for API keys, media limits, retries, and platform-specific behavior.
Getting started guide
Create an account, connect a profile, generate an API key, and publish your first supported post.
Publishing guides library
Platform limits, OAuth refresh, rate limits, webhook status tracking, and n8n workflow patterns.
Service status page
Check whether a publishing delay is local to your workflow or related to upstream platform/API availability.
Security overview
How connected-account tokens are stored, revoked, and reported if you suspect a vulnerability.
Trial pricing and seat sizing
Review the 7-day card-required trial, 1 included seat, and how one seat includes one account/profile on each supported platform.
Privacy policy
Use this page when your message is about data access, correction, export, or account deletion.
Prefer to explore first?
Start a 7-day trial with 1 seat, connect your first profile, and review the publishing API docs.