Getting Help and Support

Find out how to get help when you need it - support channels, community, and resources.

Overview

Spojit has several support channels depending on what you need: self-serve articles for common questions, Miraxa, the intelligent layer across your automation, for instant context-aware help, and the support team for anything that requires a human. Most issues can be resolved from the Help Center or Miraxa without filing a ticket.

Pick the channel that matches your urgency and the type of question. How-to questions and concept explanations belong in the Help Center; live debugging belongs with Miraxa; account, billing, or platform incidents belong with the support team.

Support Channels

Help Center - browse guides, tutorials, and connector documentation. Use the search bar at the top to jump straight to an article.
Miraxa - the intelligent layer across your automation, available from every page in the app. It knows the page you're on and, in the workflow designer, the workflow you're editing.
Email - send a message to support@spojit.com. Include your workspace name, the workflow ID if relevant, and a link to the failed execution.
Live Chat - click the chat widget in the bottom-right of this Help Center for support team conversation.
In-App Feedback - open Feedback in the sidebar to send feature requests or bug reports tied to your account.
Developer Documentation - docs.spojit.com hosts API references, connector specifications, and advanced configuration.

What to Include in a Support Request

Workspace name (visible in the workspace switcher top-left).
Workflow name and ID, if the issue is workflow-specific.
Execution ID and timestamp for failed runs.
A description of the expected behaviour vs. what happened.
Screenshots of error messages where helpful.

Tips

Try Miraxa first for "how do I" questions - it answers in seconds and is context-aware.
For failed executions, copy the execution ID from the URL into your support request so the team can find the run.
Use Feedback rather than email for feature requests - those are tracked separately.

Common Pitfalls

Sending screenshots without the execution URL. The URL is the fastest way for support to find the run.
Reporting an issue from the wrong workspace - confirm the workspace switcher shows the workspace where the problem happened.
Expecting Miraxa to see other users' workflows. It only has visibility into the workflow you're currently editing.