Build and Integrate Custom Tools with Pronnel Apps

Introduction:

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.

Accessing the Pronnel App Builder

  1. Go to your profile dropdown and open User Settings.

    Accessing User Settings
  2. Click on the My Apps section from the sidebar.

    My Apps Section
  3. Click New App to begin building your custom integration.

    Create New App Button

Filling App Details

  1. Set the App Name, Logo, Description, and select a Category (e.g., Calling App, GitApp).

    App Details Form
  2. 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.

    App Details Form
  3. 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.

  4. 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.

  5. 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.

  6. If Enable Pronnel Auth is turned ON, you will need to provide the following OAuth-related URLs:

    • Authorization URL: This is the endpoint on your server that starts the OAuth login and authorization process. When a user connects your app, Pronnel will redirect them to this URL.
      Example: https://api.myapp.com/oauth
    • Connection Validation URL: This URL is used by Pronnel to check if the OAuth token is still valid. It ensures that your app is still connected for the user.
      Example: https://api.myapp.com/validate
    • Disconnection URL: When a user disconnects the app from Pronnel, this endpoint is triggered. It should remove any tokens or sessions related to the app.
      Example: https://api.myapp.com/disconnect
    OAuth Fields in App Configuration

Setting Up OAuth

After enabling OAuth, you’ll be asked to fill the following fields:

  • Authorization URL: Endpoint to initiate the OAuth login.
  • Redirect URI: Callback URL for Pronnel to return the user after login.
  • Connection Validation URL: Checks if the app’s token is still valid.
  • Disconnection URL: Used to revoke or disconnect the user’s session.
  • Permissions: List of access scopes your app needs.
OAuth Configuration Fields

Enabling UI and Setting Panel

  1. Toggle Enable Setting Page to display a custom settings UI.

  2. Toggle Enable Item Widget to show a widget in the item view panel.

  3. Upload your static build (HTML/JS/CSS) in the provided section.

    Uploading UI Build

Defining Fields

Use the Fields section to collect configuration data:

  • Fixed Fields: Values set by you, not editable by the user.
  • Dynamic Fields: Entered by the user during app configuration (e.g., API Key, Username).
Fixed and Dynamic Fields

Adding Channels and Collaboration

  1. Add a Channel to let your app interact as a communication source in Pronnel.

  2. Invite Collaborators to manage and test the app with you.

  3. Use Version Control to manage updates and deploy stable releases.

Channel and Collaborator Settings

Setting Up Automation Triggers and Actions

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).

Step 1: Add a Trigger

  1. Click + Add Trigger.

  2. Set a name like "Customer Tag Updated".

  3. Choose a input filed like fixed or dynamic

  4. Understanding Trigger URLs

    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.

    1. 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.

    2. 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.

    3. 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.

      Unsubscribe URL setup

    Important Notes:

    • Each URL must return a valid JSON response.
    • Use HTTPS endpoints only — HTTP is not accepted.
    • All three URLs are required to complete trigger setup.
    • Test your URLs using tools like Postman or webhook.site before submitting.

Step 2: Add an Action

  1. Click + Add Action.

  2. Name it something like "Send Offer Message".

  3. Set up input fields the user will fill, like Message Content or Customer ID.

  4. Fill execution path where

    The Execution Path is the live URL your app exposes to receive automation calls from Pronnel.

    Configuring the backend logic for the action

Example Use Case

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.

Setting Up Automation Templates

  1. Go to the Automation section in the app editor.

  2. Add Triggers (what causes an automation to run) and Actions (what your app should do).

  3. Once saved, these appear in the Pronnel Automation Builder for users who install your app.

    Automation Triggers and Actions

Conclusion:

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.

FAQs

1. What is the base URL used for?

It acts as the root domain for all API calls and OAuth interactions between Pronnel and your app.

2. What does enabling "Pronnel Auth" do?

It activates OAuth fields so your app can securely connect and authenticate with users via Pronnel.

3. Can I host my app’s UI inside Pronnel?

Yes. By enabling the setting or item widget and uploading your build, your UI will render directly inside Pronnel.

4. What is the difference between fixed and dynamic fields?

Fixed fields are hardcoded for every instance, while dynamic fields are set by the user at installation.

5. What does the redirect URI do?

It is the callback route where Pronnel redirects after a user authorizes your app using OAuth.

6. How can I test my app before launching?

You can use collaborators and versioning to test privately before publishing the app to all users.

7. What kind of automations can I define?

You can add triggers (events) and actions (responses) that run when your app is installed and configured.

8. How can I let my app send messages into Pronnel?

By setting up channels, your app can send or receive messages like chatbots or notifications.

9. Can I update the app UI later?

Yes. Upload a new build in the UI section and save the changes in a new version.

10. Will disconnecting a user from the app stop all automation?

Yes. If OAuth is revoked or expired, automations and UI interactions may fail until reconnected.