Overview
Custom Apps in Workbird allow you to create your own integrations for services that are not yet available in the App Registry. They are designed to give you full control over how your workflows interact with third-party tools, private APIs, or internal systems.
Custom Apps can be:
Private – visible and usable only within your organization.
Shared Across Organizations – made available to partner or client organizations.
Public – listed in the App Registry for all Workbird users (requires review and approval before publishing).
How Custom Apps Work
Custom Apps are built around two core concepts:
1. Triggers
Triggers listen for events from an external service and start a workflow in Workbird when those events occur. Examples:
“New customer created” in a CRM
“New message received” in a chat application
“File uploaded” to a cloud drive
2. Actions
Actions perform operations in an external service when invoked from a workflow. Examples:
Send an email
Create a new task
Update a database record
Note: While you can build both triggers and actions, we encourage using AI Agents or MCP Servers where possible, as they are more powerful, flexible, and easier to maintain for complex integrations. Actions are still supported for simpler, direct API operations.
Creating a Custom App in the App Registry
Open the App Registry – Navigate to the “Custom Apps” section.
Create New App – Provide details such as the app name, description, category, and logo.
Configure Authentication – Define how Workbird should authenticate with the external service (e.g., API key, OAuth).
Add Triggers and Actions –
Triggers: Define events to listen for.
Actions: Define tasks Workbird can perform in the external service.
Test Your App – Ensure triggers and actions work as intended.
Publish or Share –
Keep it private for your organization
Share with specific organizations
Submit for public listing (requires approval)
Public App Approval Process
If you choose to make your app public:
Submit the app for review directly in the App Registry.
Our team will validate the app for quality, security, and compliance.
Once approved, it will be available to all Workbird users in the public App Registry.
Why Build a Custom App?
Integrate with internal tools or niche services.
Replace repetitive manual processes with automation.
Extend Workbird’s capabilities to meet your unique needs.
Share valuable integrations with clients, partners, or the broader Workbird community.
Last updated