Skip to main content
Version: Next (nightly)

Integrations

Cobblr can talk to the services you already use: Slack, Discord, email, SMS, and anything that speaks webhooks. This page is the how. For the full list of everything Cobblr connects to, see the Integration catalog.

To send something out:

  1. Set up a channel under Me then Notification channels.
  2. Wire an entity event to it (or put the wire on a schedule).

Fire on events (outbound)​

Wire an entity event to an outside service. You choose the event and where it goes.

  • An order arrives, post to a Slack channel.
  • A task is finished, ping a Discord webhook.
  • 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​

Channels are set up under Me then Notification channels (see Notifications), 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, and covers anything else.
  • Email sends through a delivery provider you configure on the subscription itself (SMTP, or a transactional provider like Mailgun, Resend, or Postmark).
  • SMS goes through your own Twilio account.
  • What can trigger any of them is the event vocabulary described under Notifications.

Each destination carries its own sending setup.

Reaching something on your own network​

  • Self-hosted on the same network: a webhook or a connection pointed at a LAN address works with nothing else to set up.
  • 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. That network never has to accept an inbound connection.
  • For mirroring a local source in, see Syncing from other systems.
What the bridge path is for

That is the path for a local inventory app to mirror in, a machine, or local AI.

Your calendar app​

Paste the workspace calendar's tokenized .ics URL into "From URL" and everything dated in the workspace shows up beside your other calendars.

  • That feed is the whole Google Calendar and Apple Calendar integration. No account linking.
  • The token is the secret, and rotating it cuts off every shared copy.

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.