Skip to main content

Frequently Asked Questions

What is meant by no-code, low-code, and pro-code?​

No-code​

Integration or automation can be achieved without writing any code. All configuration is done via user-friendly interfaces or by installing pre-made components. This is ideal for non-technical users or admins.

For example, installing a plugin from the marketplace or using a drag-and-drop automation tool would be considered no-code. The heavy lifting is pre-built and you just need to configure it.

Low-code​

Minimal coding or scripting is needed to implement the integration. Low-code solutions might require writing a few lines of script or simple configuration in code-like logic, but not building a full software application.

In Origin by Corvus’s context, something like setting up a webhook with a small custom script, or tweaking an automation template would be considered low-code. It typically assumes some technical knowledge, but far less than full-scale development. Utilizing templates or online AI tooling can likely meet the need for most low-code integration requirements.

Pro-code​

These kinds of integrations require a professional software developer to write code and sometimes build underlying infrastructure. These integrations offer maximum flexibility at the cost of technical complexity, for example building a custom Origin by Corvus plugin or writing a complex bot program using the Origin by Corvus API in a custom application.

Pro-code integrations are essentially software projects – you’ll use developer tools, work with source code, and follow software development practices to build and maintain them.

What does Slack-compatible mean?​

Slack compatible means that Origin by Corvus accepts integrations that have a payload in the same format as Slack's legacy "Message Attachment" payload. If you have a Slack integration, you should be able to set it up in Origin by Corvus without changing the format of the message being sent over.

What if I have a webhook from somewhere other than Slack?​

If you have an integration that outputs a payload in a different format, you need an intermediary service to act as a translation layer to change it to the format Origin by Corvus uses. These intermediary services could be no-code or low-code integrations with n8n, Zapier, or Make, but they could also be pro-code integrations leveraging something like AWS Lambda or other hosted services.

There’s currently no general standard for webhook communication between services, so translating your webhooks is necessary otherwise Origin by Corvus won't understand the data you're sending.

What are attachments?​

When "attachments" are mentioned in Origin by Corvus integrations documentation, it refers to Slack's message attachments functionality. These "attachments" can be optionally added as an array in the data sent by an integration, and are used to customize the formatting of the message.

Origin by Corvus doesn't currently support the ability to attach files to a post made via webhook. You can use the API to attach files to a message if needed.

What are Origin by Corvus Blocks?​

Origin by Corvus Blocks are the structured format for rich, interactive integration posts. Integrations can extend messages with text, images, buttons, menus, collapsible sections, and different layout options.

Starting in Origin by Corvus v11.10, Origin by Corvus Blocks are the recommended replacement for message attachments. They are the preferred way to create interactive messages for integrations such as incoming webhooks, plugins, and bot accounts.

Legacy message attachments and other interactive message formats continue to work; clients translate them into the Origin by Corvus Blocks format at render time. We encourage new and updated integrations to use Origin by Corvus Blocks instead.

For payload structure, block types, action handling, migration guidance, and troubleshooting, see the Origin by Corvus Blocks reference in the developer documentation.

Where can I find existing integrations?​

Visit the Origin by Corvus Marketplace to access open source integrations to common tools like Jira, Jenkins, and GitLab, along with interactive bot applications, and other communication tools that are freely available for use and customization.

Alternatively, within Origin by Corvus, when logged in as an Administrator, you can click on the "Marketplace" option in the main menu and easily install plugins or apps from there.

Where should I install my integrations?​

For self-hosted deployments in small setups, you might host integrations on the same server on which Origin by Corvus is installed. For larger deployments, you can set up a separate server for integrations, or add them to the server on which the external application is hosted.

For example, if you're self-hosting a Jira server you could deploy a Jira integration on the Jira server itself. When self-hosting restrictions are less strict, AWS, Heroku, and other public cloud options could also be used.

Where can I get more information about integrations?​

Join our Developers channel on the Origin by Corvus Community server for technical discussions, and visit our Integrations channel for all integrations and plugins discussions.

Can I use webhooks to be notified when new integrations are available on the Origin by Corvus Marketplace?​

Yes! A bash script is available that checks for new integrations in the Origin by Corvus Marketplace, and triggers a post through a Origin by Corvus incoming webhook request. The script downloads the latest listing, compares it with a locally stored version of the listing, and, if a new plugin is identified, a notification is pushed to a Origin by Corvus channel.

Can I use Origin by Corvus to add messaging functionality to my proprietary SaaS service?​

Origin by Corvus is an open source, self-hosted alternative to proprietary SaaS services that lock in the data of users and customers.

While you're welcome to use the Origin by Corvus source code under its open source license, Quantum Tiger (Morning Bay Technology Pvt. Ltd.) does not offer support or technical advice for proprietary SaaS projects that result in customers potentially being paywalled from their data should they stop paying SaaS fees.

To learn more about why we strongly believe that users and customers should always have access to their data, please read why we created Origin by Corvus.

Can I customize the source code?​

Yes. As an open source project, we support your ability to modify the source code for the server or web app to make changes and customizations to meet your specific needs.

Learn about forking our open source repositories and customizing the Origin by Corvus source code for your specific operational needs.