Connecting a toolkit
Every toolkit connects the same way, because none of them has code of its own here.
In the console
Find it in the directory
Connectors → Add, then search. The directory is served live from the integration provider, so anything listed is connectable today.
Start the connection
Memnox asks the provider for a connect URL and sends you to the tool's own consent screen.
Approve the consent screen
Read what is being asked for. Whose name appears on this screen depends on whether your admin registered your own OAuth app, see Your own OAuth app.
Subscribe to a trigger
A connection with no trigger produces nothing. This is the step people skip, and then wonder why Activity is empty.
Reconcile people
Immediately. Author trust is decided at ingestion and never re-judged, so linking identities now means the first week of events is classified correctly.
Console → Connectors, mid-connection with the consent screen visible
screenshot slot, save as public/screens/…png and set src
What to set up right after
The permalink base URL
Some toolkits do not send a link. Slack sends a channel and a timestamp; Jira sends an issue key. Memnox composes the permalink from a base URL you set once, under Settings → Permalinks.
Without it, those events are rejected rather than stored without evidence. Set it in Settings → Permalinks before the first event arrives.
Identity linking
Ten minutes here removes most of the confusing taint you will otherwise spend weeks explaining. See People.
The two things that go wrong
Connection limits
How many sources you may connect at once is a plan limit. Settings → Billing shows your current allowance and how much of it is in use, and a connection that would exceed it is refused with a clear reason rather than half-created.
Executing tools
A connection does two things: it lets events flow in as source events, and it exposes the tool's own actions so Memnox can act out through it. Posting a Slack message, transitioning a Jira issue, merging a pull request.
Tool execution is a governed action like any other. It goes through the same gate, with the same audit event, and nothing bypasses the decision path because it came from an integration. Wrapping those actions is covered in How integrations work.