Skip to main content
When something is not working — or you just want a person to look at it — this page tells you who to contact, what to include so they can help fast, and how to check whether the issue is on ModuleX’s side.

Contact support

Email the team. Include your organization ID, what you were doing, and any error code.

Check system status

See whether the platform and its health checks are up before you report a problem.

Join the community

Ask questions and share workflows with other ModuleX users.

Contribute

Found a gap or want to add an integration? Here is how to help.

​
Frequently asked questions

Email support@modulex.dev. To get help fast, include three things: your organization ID, what you were doing when it happened, and any error code you saw (for example 402 or 403). See what to include below for the full list, and Errors & troubleshooting to decode an error code first.
Your organization ID, a short description of what you were doing, and any error code or message. The more specific you are, the faster the team can reproduce it. See the checklist below.
It is the value you send in the X-Organization-ID header on API calls, and it is shown in the app’s organization settings. Learn how the org context works in Org context & X-Organization-ID.
ModuleX exposes a public liveness check at GET /system/health, documented on the System status & health page, so you can confirm the API is up. A hosted status / incident page (with uptime history and live incident updates) is not confirmed yet — see Is there a hosted status or incident page? below.
Support depends on your plan: Free uses the community, Pro adds Discord, Max adds email plus Discord, and Enterprise includes dedicated support. See Support by plan below, and Plans & pricing for the full comparison.
Join the ModuleX Discord at discord.gg/jEyCABwU9E to ask questions and share workflows. You can also open issues on GitHub at github.com/ModuleXAI. More detail in Where can I ask the community? below.
File it on GitHub at github.com/ModuleXAI, or email support@modulex.dev if it involves your account or data. If you want to fix or add something yourself, see Contributing.
A few flows are documented gaps rather than bugs (for example, deleting several nodes at once, or the “refresh OAuth” button). Check Known limitations before you file a report — your issue may already be listed with a workaround.

​
How do I contact support?

Email support@modulex.dev. A clear first message saves a round trip — include the details below.
Support is a paid-plan benefit. Free accounts are pointed to the community channels; paid plans add direct support. See Support by plan.

​
What should I include in a support request?

1

Your organization ID

The ID of the organization you were working in — the same value you send as the X-Organization-ID header. It tells the team exactly which account and data to look at. See Org context & X-Organization-ID.
2

What you were doing

A short, concrete description: the action you took, the workflow or chat involved, and what you expected to happen versus what actually happened.
3

Any error code or message

Copy the exact error code (for example 402, 403, or 429) and any message text. If you are not sure what it means, Errors & troubleshooting explains the common ones first.
4

When it happened

The approximate date and time, and whether it is still happening or was a one-off. This helps the team line your report up with logs.

​
Is there a status page?

To check whether the platform itself is up, use the health endpoints documented on the System status & health page — GET /system/health is a public liveness check that returns the service status without authentication.

​
Is there a hosted status or incident page?

A hosted status / incident page (uptime history, live incident posts) is not confirmed in the current sources. Until one is published, use the health endpoints to verify the API is reachable, then contact support if it is up but your action still fails. TBD — this page will link to a hosted status page once one exists.

​
What support do I get on my plan?

The support channel scales with your plan. Confirm the current details on Plans & pricing.
Enterprise teams also get hands-on onboarding and a dedicated support contact. See ModuleX for enterprise and Contact sales.

​
Where can I ask the community?

For questions, ideas, and sharing workflows, the community is the fastest place to start — and the primary support channel on the Free plan.

Discord

Chat with other ModuleX users and the team at discord.gg/jEyCABwU9E.

GitHub

Report bugs, request features, and browse the code at github.com/ModuleXAI.

​
Before you reach out

A quick self-check often resolves the issue faster than waiting for a reply.

Decode the error

Common codes like 401, 402, 403, and 429 each have a known cause and fix.

Check known limitations

Some behaviours are documented gaps with workarounds, not bugs.

Confirm the platform is up

Use the health endpoints to rule out a platform-wide issue.