Pronnel Apps enable you to connect external tools and services—like calling platforms, Git repositories, or CRMs—directly into your Pronnel workspace. You can create an app, define OAuth authentication, show custom UI, set automation triggers/actions, and configure permissions to build flexible integrations.
Go to your profile dropdown and open User Settings.
Click on the My Apps section from the sidebar.
Click New App to begin building your custom integration.
Set the App Name, Logo, Description, and select a Category (e.g., Calling App, GitApp).
Enter the Base URL — this is your app’s root endpoint that handles all API communications like authentication, data syncing, or webhook callbacks.
Example: If your backend is hosted at https://api.myapp.com
, this will be your Base URL. Pronnel uses this as the root path to reach your app’s endpoints such as /oauth
, /validate
, etc.
Toggle Enable Pronnel Auth if your app requires the user to log in through an external platform using OAuth. This enables secure access to protected data in your app.
Once enabled, additional fields for setting up OAuth will appear.
Toggle Enable Settings Page if your app includes a custom settings interface that users can configure inside Pronnel. For example, setting tokens, filter rules, or preferences related to the app.
You will later upload a build that defines the UI shown in this settings tab.
Toggle Enable Item Widget if you want your app to display custom information or interactions inside the Pronnel item side panel. This is useful for integrations like ticket status, issue logs, or recent activities.
If Enable Pronnel Auth is turned ON, you will need to provide the following OAuth-related URLs:
https://api.myapp.com/oauth
https://api.myapp.com/validate
https://api.myapp.com/disconnect
After enabling OAuth, you’ll be asked to fill the following fields:
Toggle Enable Setting Page to display a custom settings UI.
Toggle Enable Item Widget to show a widget in the item view panel.
Upload your static build (HTML/JS/CSS) in the provided section.
Use the Fields section to collect configuration data:
Add a Channel to let your app interact as a communication source in Pronnel.
Invite Collaborators to manage and test the app with you.
Use Version Control to manage updates and deploy stable releases.
Automation allows your app to perform tasks or respond to events within user workflows. In the App Editor, you can define Triggers (events that start an automation) and Actions (tasks that your app performs).
Click + Add Trigger.
Set a name like "Customer Tag Updated".
Choose a input filed like fixed or dynamic
When setting up a Trigger in your app's automation, you must provide three important URLs. These define how Pronnel interacts with your backend when the trigger is configured, used, or deleted.
Sample Response URL
This URL is called when the automation setup form is loaded and all required fields are filled by the user. It should return a static or mock JSON object that shows the sample output structure of your trigger.
Use this to help users understand what data your trigger will emit.
Subscribe URL
This endpoint is called when the trigger is activated in a board (after user installs the app and automation). Pronnel will pass dynamic values based on the user’s configuration. Your server should then subscribe to events (e.g., item created, tag added, etc.) and respond with a success acknowledgment.
Unsubscribe URL
When a user deletes or disables the trigger, this URL is called to clean up any webhook or event listeners on your end. Use it to remove any server-side subscriptions or tracking tied to that automation.
Important Notes:
Click + Add Action.
Name it something like "Send Offer Message".
Set up input fields the user will fill, like Message Content or Customer ID.
Fill execution path where
The Execution Path is the live URL your app exposes to receive automation calls from Pronnel.
Trigger: Lead is tagged as “Interested”
Action: App sends a WhatsApp message offering a discount
This can be part of a larger automated sales flow initiated by your app.
Go to the Automation section in the app editor.
Add Triggers (what causes an automation to run) and Actions (what your app should do).
Once saved, these appear in the Pronnel Automation Builder for users who install your app.
Pronnel Apps empower teams to bring third-party tools into their workflow, streamline authentication, show contextual UI, and automate tasks. From Git integrations to calling platforms, you can fully customize how your external service interacts with Pronnel.
It acts as the root domain for all API calls and OAuth interactions between Pronnel and your app.
It activates OAuth fields so your app can securely connect and authenticate with users via Pronnel.
Yes. By enabling the setting or item widget and uploading your build, your UI will render directly inside Pronnel.
Fixed fields are hardcoded for every instance, while dynamic fields are set by the user at installation.
It is the callback route where Pronnel redirects after a user authorizes your app using OAuth.
You can use collaborators and versioning to test privately before publishing the app to all users.
You can add triggers (events) and actions (responses) that run when your app is installed and configured.
By setting up channels, your app can send or receive messages like chatbots or notifications.
Yes. Upload a new build in the UI section and save the changes in a new version.
Yes. If OAuth is revoked or expired, automations and UI interactions may fail until reconnected.