Marketplace & Integrations
The Marketplace connects Omnisnia to tools your team already uses. Installing an app does two things: it subscribes a delivery URL you supply to your CRM events, and it issues that app a scoped API key so it can call back into the API. Uninstalling removes both.
Open Marketplace in the navigation. It is available on every plan.
What is in the catalog
Four first-party connectors ship today. All four receive the same CRM events; they differ in what they expect at the other end.
| App | What it is for |
|---|---|
| Outgoing Webhooks | Any HTTPS endpoint you control — your own service, or a tool not listed here |
| Slack | Posts events into a Slack channel, reshaped as chat messages |
| Zapier | Triggers Zaps; events arrive as raw JSON on a Catch Hook |
| Make | Triggers Make scenarios through a custom-webhook trigger URL |
Each app is a card showing its name, publisher, description, and the scopes it will be granted. An installed app is marked Installed.
Install an app
- Click Install on the app’s card.
- Fill in the Delivery URL — where this app receives your CRM events. For Slack that is an Incoming Webhook URL; for Zapier a Catch Hook URL; for Outgoing Webhooks, your own HTTPS endpoint.
- Review the scopes listed under This app will be granted.
- Click Install.
Omnisnia then shows the app’s API key and webhook signing secret.
Copy them now — they are shown only once. The API key authenticates the app’s calls into your CRM; the signing secret lets it verify that a delivery genuinely came from Omnisnia. Neither can be retrieved again afterwards. If you lose them, uninstall and reinstall the app to be issued a new pair.
Delivery
Events are delivered through the CRM’s durable webhook queue. A delivery that fails is retried up to five times with a widening gap between attempts (one minute, five, thirty, two hours), and is dead-lettered rather than silently dropped once those are exhausted. Slack installs get the Slack message format; every other app gets the raw event JSON.
Uninstall
Uninstall on an installed card tears down what the install created — the webhook subscription stops delivering, and the app’s API key stops working.
Building your own integration
You do not need a catalog entry to integrate. Install Outgoing Webhooks
against your own endpoint, or use a per-tenant API key
directly. The scopes an integration can request are listed at
/api/v1/oauth/scopes on your server — the View the developer scopes link at
the bottom of the Marketplace screen opens it.
Related pages
- Account & Organizations — API keys and organization settings
- Workflow Automation — acting on events inside the CRM
- Custom Objects — extending the data model itself