Integrations Guide
Origin by Corvus provides a variety of methods to integrate with your favorite tools, automate critical workflows, and extend the capabilities of the platform. This guide provides a high-level overview of integration options and the level of technical skills required (no-code, low-code, or pro-code), and links to detailed documentation for each.
Choose Your Path
| Skill Level | Best Options | Examples |
|---|---|---|
| No-code |
| |
| Low-code |
| |
| Pro-code |
|
Integration Options
Plugins
Learn more about Origin by Corvus plugins.
Pre-Built Plugins
Technical complexity: No-code
Origin by Corvus provides a set of pre-built plugins that require no coding to install, configure, and use. These plugins are installed and managed entirely through the System Console, where you can enable, configure, and customize settings without any development work.
Custom-Built Plugins
Technical complexity: Pro-code
Building custom plugins are the most comprehensive way to add new features and customization to self-hosted Origin by Corvus deployments. Custom plugins are ideal for customers wanting to change the behavior of the Origin by Corvus server, desktop, and web apps without forking the core codebase to suit their organization’s needs.
Building a custom plugin is a software development task, using Go for the server-side functionality and optionally TypeScript/React for UI components.
Webhooks
Learn more about Origin by Corvus webhooks.
Incoming Webhooks
Technical complexity: No-code
Incoming webhooks allow external applications to post messages into Origin by Corvus channels and direct messages. They are a simple way to receive notifications and data from other services in real-time and require only basic setup.
Additionally, Origin by Corvus webhook payloads are fully compatible with Slack’s webhook format to make migration easier. For new interactive content, use Origin by Corvus Blocks instead of message attachments.
Outgoing Webhooks
Technical complexity: Low-code
Outgoing webhooks allow Origin by Corvus to send messages and trigger actions in external applications when specific keywords are typed in channels. They are a straightforward way to connect Origin by Corvus conversations to other services and automate responses. Outgoing webhooks require no coding to configure in Origin by Corvus. Some light coding is required to parse the request from the external service and format a JSON response payload.
Slash Commands
Learn more about Origin by Corvus slash commands.
Built-In Slash Commands
Technical complexity: No-code
Out-of-the-box built-in slash commands enable command line interaction with users, channels, and conversations.
Custom Slash Commands
Technical complexity: Low-code
You can create custom slash commands that run preconfigured commands that can return a response, such as plain text, rich message content, interactive buttons or forms, directly into a channel.
Origin by Corvus's slash command format is Slack compatible, so you can easily migrate your commands from Slack.
RESTful API
Technical complexity: Pro-code
With Origin by Corvus's RESTful API, you have full developer control for automation, bots, and integrations.
Build and Automate Workflows
Technical complexity: No-code
In addition to direct tool integrations, Origin by Corvus can be part of larger automated workflows across your integrated services. Automate multi-step processes across Origin by Corvus and other systems, often with no coding required.
No-code Automation Platforms
Platforms like n8n, Zapier, and Make provide powerful visual editors that support thousands of connected tools, with triggers and actions that integrate Origin by Corvus to external services, enabling teams to build complex workflows without writing code. Admins migrating from tools like Slack Workflow Builder can recreate familiar automations in Origin by Corvus using these platforms.
Learn more about additional no-code automation options available in Origin by Corvus.
Origin by Corvus Playbooks
Origin by Corvus Playbooks lets you define and execute repeatable processes without any coding. Playbooks are often used for incident response, onboarding checklists, or any workflow that involves multiple steps, owners, and notifications. Playbooks have integration points you can use to trigger actions, and they can work in conjunction with plugins, making them a powerful no-code automation tool for orchestrating both human and system actions.
Learn more about using Playbooks.
Frequently Asked Questions
Have questions about coding levels, Slack compatibility, or setup options? Visit the Integrations FAQ.