Skip to main content

Integrations

For the full list of everything Cobblr connects to, see the Integration catalog. This page is the how.

Cobblr can talk to the services you already use: Slack, Discord, email, SMS, and anything that speaks webhooks.

Fire on events (outbound)​

Wire an entity event to an outside service. An order arrives, post to a Slack channel. A task is finished, ping a Discord webhook. You choose the event and where it goes. For getting told in-app instead, see Notifications. Browser push is built but not delivering yet, so treat in-app and webhooks as the channels you can rely on today.

Receive pings (inbound)​

Cobblr can also take an external ping over a webhook, so another system can poke your workspace when something happens on its side. For mirroring another system's records into Cobblr wholesale, see Syncing from other systems.

Channels​

Slack, Discord, email, and SMS are built in, and a plain webhook covers anything else. Each connection is set up per workspace, so two workspaces on the same instance can wire to entirely different places. Slack and Discord take an incoming-webhook URL pasted into the connection; a plain webhook takes whatever URL you give it. Email sends through a delivery provider you configure on the subscription itself (SMTP, or a transactional provider like Mailgun, Resend, or Postmark), and SMS goes through your own Twilio account, so each destination carries its own sending setup. What can trigger any of them is the event vocabulary described under Notifications.

Reaching something on your own network​

A self-hosted Cobblr sitting on the same network as your other systems reaches them directly, so a webhook or a connection pointed at a LAN address works with nothing else to set up. When the thing you want to reach is somewhere Cobblr can't get to (behind a firewall, or at a second site), use an edge bridge: a small agent you run next to it that dials outward to your Cobblr and carries each request from there, so that network never has to accept an inbound connection. That is the path for a local inventory app to mirror in, a machine, or local AI. For mirroring a local source in, see Syncing from other systems.

On a schedule​

A wire doesn't have to wait for an event. Any wire can fire on a repeating rule instead, using the standard iCal format: every Monday at 9, the first of every month. That covers the routine work, a recurring task, a monthly stock check, a maintenance reminder, described once and kept to.