What details need to be shared with the NoPaperForms (NPF) team for MyOperator integration?

What details need to be shared with the NoPaperForms (NPF) team for MyOperator integration?

🧭 Table of Contents

🧠 Overview

To integrate MyOperator with NoPaperForms (NPF), specific technical details must be securely shared with the NPF team. These details ensure smooth integration, proper configuration of features like Click-to-Call, and effective communication between MyOperator and the NPF system. Sharing the required details correctly is crucial to ensure real-time data sync and smooth call management.

🔝 Back to top ⬆️

🔑 Key Details to Share with NPF

To successfully configure and integrate MyOperator with NoPaperForms (NPF), you need to share the following details:

1️⃣ API Credentials & Access Tokens

  • API Token: Found in the APIs & Webhook section in the MyOperator panel under Calling API.
  • Company ID: Identifies your MyOperator account.
  • Secret Token: Found in the Calling API section for authentication.
Important: Always share these credentials through a secure channel (e.g., encrypted email or a shared vault).

2️⃣ Testing & Documentation Tools

  • Click-to-Call API Documentation: Share the official MyOperator API docs (include link if available).
  • Postman Collection: Export and share the Postman collection with test call setups to validate integration.

3️⃣ Feature Configuration Status

Ensure the NPF team is aware that the following MyOperator features are enabled for smooth integration:

  • Webhook – In-Call
  • Webhook – After-Call
  • Input Node
  • Anonymous User ID
  • OBD/Click-to-Call (if outbound features are expected)

4️⃣ Expected URL Triggers from NPF

Ensure the NPF team provides the following endpoint URLs for webhook configuration:

  • getCounsellor URL: Fetches counsellor mapping based on incoming numbers.
  • ivrCallNotification URL: Sends live call updates during ongoing calls.
  • ivrCallBackDetails URL: Receives call summaries after the call ends.
Goal: These URLs ensure smooth data exchange between MyOperator and NPF, allowing for real-time call tracking and assignment.

🔝 Back to top ⬆️

⚙️ Step-by-Step Process for Sharing the Details

Follow these steps to ensure all integration details are shared securely and correctly with the NPF team:

Step 1: Gather API Credentials

  1. Log in to the MyOperator Panel.
  2. Go to APIs & Webhook and copy the API Token, Company ID, and Secret Token.
  3. Ensure that the credentials are active and unexpired.

Step 2: Share Testing & Documentation Tools

  1. Provide the Click-to-Call API documentation.
  2. Export and share the Postman collection for test calls.

Step 3: Confirm Feature Configuration

  1. Verify that the following features are enabled in MyOperator:
    • In-Call Webhook
    • After-Call Webhook
    • Input Node
    • Anonymous User ID
    • OBD/Click-to-Call (if required for outbound calls)
  2. Inform NPF that these features are enabled and ready for integration.

Step 4: Share URL Triggers

  1. Ensure the NPF team shares the following endpoint URLs:
    • getCounsellor URL
    • ivrCallNotification URL
    • ivrCallBackDetails URL
Goal: This step ensures that all technical configurations are in place before the integration process begins.

🔝 Back to top ⬆️

✅ Final Checklist Before Sharing Details

Before finalizing the integration, confirm the following:

  • ✅ All API credentials (API Token, Company ID, Secret Token) are active and correct.
  • ✅ The Click-to-Call API docs and Postman collection have been shared.
  • ✅ Required MyOperator features (In-Call Webhook, After-Call Webhook, Input Node, Anonymous User ID) are enabled.
  • ✅ The NPF team has the correct URL triggers (getCounsellor, ivrCallNotification, ivrCallBackDetails).
  • ✅ Testing completed for all webhooks and features.
Goal: Ensure all details are properly shared and the integration can be completed without any issues.

🔝 Back to top ⬆️

❓ FAQs

Q1. Why do I need to share API credentials with the NPF team?
A. API credentials such as the API Token, Company ID, and Secret Token are required to authenticate and enable secure communication between MyOperator and NPF.

Q2. How do I verify that all webhooks are working correctly?
A. After setting up the webhooks in the MyOperator panel, conduct test calls to verify that the ivrCallNotification and ivrCallBackDetails URLs are receiving live updates and call summaries as expected.

Q3. What should I do if the NPF team hasn't received the correct URLs?
A. Double-check that the URLs are shared in the correct format and test them with the NPF team before finalizing the integration.

Q4. What is the importance of the getCounsellor URL?
A. The getCounsellor URL ensures that the correct counsellor is assigned to a call based on the incoming number. This URL must be configured to route calls to the correct agent.

🔝 Back to top ⬆️

🔗 Related Articles

  • Setting Up Webhooks in MyOperator
  • NPF Integration Troubleshooting Guide
  • How to Configure Call Flows in MyOperator

🔝 Back to top ⬆️

🏷️ Keywords

MyOperator integration, NoPaperForms, API credentials, webhook configuration, Click-to-Call, real-time data sync, counsellor routing, integration setup, lead tracking, outbound calling