Request a connector or a feature

StackJack adds connectors and features from what customers ask for. This page says where to ask, what to include, and where to follow a request once it is in.

Where to ask

Use the Feedback button in the Portal header. It opens StackJack's Feature Request board, where you can post a request, comment on one, and vote for requests other people have already posted.

• Search the board first. If the connector or feature is already requested, vote for it and add a comment with your use case. Votes and use cases are what move a request up.
• One request per post. A post that asks for three things is hard to vote on and hard to track.
• The board is public. Other customers can read your post and its comments. Do not include customer names, credentials, ticket contents, or anything else you would not publish. See Support versus Feedback.

If something is broken or blocking you, that is a support question, not a feature request: open a support conversation instead. See Getting help.

Ask in the StackJack Discord

The StackJack bot in the Discord server checks the roadmap and adds requests for you.

• /roadmap (or !roadmap) followed by a topic, for example /roadmap Halo, shows the matching requests with their status and votes, and a link to vote. It answers only from the roadmap. It never gives dates.
• /feature (or !feature) followed by what you need, for example /feature export HaloPSA tickets to CSV. If the request is already on the roadmap, the bot links it so you can vote. If it is not, the bot adds it. If the bot is not sure, it shows the closest requests and an Add as a new request button that only you can press.
• A new connector needs a link to the vendor's API documentation in the request, or a spec file attached to the !feature message. Without one, the bot tells you what to add and adds nothing. The bot does not open your link.
• A request the bot adds waits for the team's review, then shows on the roadmap. It is public, with your Discord username.
• If you mention a feature idea in a help channel, the bot may reply with the matching request to vote on, an Add to roadmap button that only you can press, a link to the connector's docs when StackJack already has it, or a note asking for a link to the vendor's API docs when you ask for a new connector. It adds nothing unless you press the button.

To have a request removed, ask the team in the server. See StackJack Discord bot privacy.

What to include in a connector request

A useful connector request names:

1. The product and vendor, and the edition you run (cloud or self-hosted, and the plan tier if the vendor's API differs by tier).
2. What you want your AI assistant or automations to do with it — for example, "list open alerts and close the ones a script already fixed". Concrete jobs decide which parts of the vendor's API are built first.
3. Whether the vendor publishes an API and where its documentation is, if you know.

Follow a request

• The roadmap is at feedback.stackjack.io — the Roadmap link at the top of this help center. It shows each request's status as it moves.
• The changelog is at feedback.stackjack.io/changelog — the Changelog link. New connectors and features are announced there when they ship.
• A post you created or voted for gets its status changes and comments, rather than a support reply.

The docs do not give release dates. A connector the Portal shows as Coming soon is listed but cannot be configured yet; the connectors you can connect today are listed in How connectors work.