Account, integrations and API

64 articles Vitor By Vitor

Everything About Reselling Papo Global

https://www.youtube.com/watch?v=jAg2bL9z6xY Everything About Reselling Papo Global EVERYTHING YOU NEED TO SELL PAPO GLOBAL WITHOUT PAID TRAFFIC 10 Sales Strategies for Resellers - From Basic to Advanced Introduction Papo Global is a complete WhatsApp automation solution that brings together AI, CRM and sales automation. As a reseller, you have a unique opportunity to help small and medium-sized businesses transform the way they work through technology. Why Is Papo Global a Unique Opportunity? - Growing Market: WhatsApp is one of the main customer service channels for small and medium-sized businesses - High Demand: Many businesses already serve customers and sell through WhatsApp and need to organize that customer service - Visible Return: With AI and automation, customers get fast replies 24 hours a day, and no lead goes unanswered - Competitive Edge: AI, CRM and automations in a single dashboard The 10 Sales Strategies (Ranked by Ease and Results) 1 Direct WhatsApp Sales EASY The simplest and most effective strategy: use WhatsApp itself to demonstrate the power of the system. How to Implement: 1. Build a list of potential customers (local businesses) 2. Send a personalized message introducing the system 3. Demo the system live over a video call 4. Offer a 7-day free trial 5. Close the sale with a special discount Sample Message: "Hi [Name]! I noticed your company is growing. I have a solution that can automate a large part of your WhatsApp customer service and help you sell more. Can I show you in 5 minutes?" 2 Online Demos EASY Webinars and live streams showing the system in action to larger audiences. How to Implement: 1. Host a weekly webinar: "Automate your WhatsApp in 30 minutes" 2. Use platforms such as Zoom, Google Meet or YouTube Live 3. Show real success stories 4. Offer exclusive bonuses to attendees 5. Follow up personally after the event 3 Content Marketing EASY Create valuable content that naturally attracts interested prospects. How to Implement: 1. Publish daily posts about WhatsApp automation 2. Make short videos with practical tips 3. Write articles about market trends 4. Share real success stories 5. Use relevant hashtags (#WhatsAppBusiness #Automation) 4 Strategic Partnerships MEDIUM Alliances with other professionals who serve the same audience. How to Implement: 1. Identify accountants, lawyers and marketing consultants 2. Offer a 20-30% commission per referral 3. Create presentation material for partners 4. Hold monthly alignment meetings 5. Share results and success stories 5 Direct Sales (Digital Door-to-Door) MEDIUM A proactive approach targeted at specific companies. How to Implement: 1. Research local businesses that use WhatsApp 2. Analyze their profiles and needs 3. Prepare a personalized proposal 4. Reach out via LinkedIn or email 5. Schedule a personalized demo Outreach Script: "Hi [Name], I saw that your [industry] company is growing. Many of my clients in the same field are using our solution to automate WhatsApp and reply to customers faster. Can I show you how it works?" 6 Groups and Communities MEDIUM Active participation in groups of entrepreneurs and business owners. How to Implement: 1. Join WhatsApp, Telegram and Facebook groups 2. Help other members with free tips 3. Share relevant content (not just sales pitches) 4. Spot natural opportunities 5. Reach out privately when appropriate 7 Events and Talks MEDIUM Presence at industry events for networking and demos. How to Implement: 1. Attend local business fairs 2. Offer free talks about automation 3. Prepare demo material 4. Collect contacts from interested people 5. Follow up personally 8 Email Marketing MEDIUM An automated email sequence to nurture leads. How to Implement: 1. Build an email list of prospects 2. Develop a sequence of 7-10 emails 3. Offer valuable content in every email 4. Include clear calls to action 5. Monitor open and click metrics 9 Influencers and Affiliates HARD An affiliate program to expand your reach exponentially. How to Implement: 1. Create an affiliate program with attractive commissions 2. Develop marketing material for affiliates 3. Recruit influencers in the industry 4. Offer training and support 5. Monitor performance and optimize 10 Corporate B2B Sales HARD An approach for large companies and corporations. How to Implement: 1. Identify companies with more than 100 employees 2. Research the decision-makers (CIO, CMO) 3. Prepare an enterprise proposal 4. Demonstrate ROI and corporate benefits 5. Negotiate long-term contracts Approach Categories Digital (Easiest) - Direct WhatsApp - Social media - Email marketing - Online webinars Relationships (Medium) - Strategic partnerships - Groups and communities - In-person events - Networking Corporate (Hardest) - B2B sales - Affiliate program - Enterprise licenses - Specialized consulting Resources and Support Materials - Channel - Official Website: Papo Global - Sales Materials: Presentations, demo videos, success stories - Recommended Tools: CRM, email automation, analytics - Communities: WhatsApp Business, LinkedIn and Facebook groups Tips for Success Core Principles - Focus on Value: Always show clear benefits, not just features - Personalize: Every customer is unique, so adapt your approach - Test and Optimize: Measure results and adjust your strategies - Build Relationships: Sales are about people, not products - Stay Up to Date: The market changes quickly Get Started Right Now! The strategies are ordered from easiest to most complex. We recommend starting with the first 3 strategies, which are simpler to implement and already deliver quick results. As you gain experience and confidence, you can move on to the more sophisticated strategies. Remember: Success in selling Papo Global depends more on your consistency and dedication than on the strategy you choose. Pick an approach that fits your profile and execute it with excellence. Start free on Papo Global → First user $0, no credit card. Learn more at papo.global.

How to Create Webhooks in the Multi-agent Service Center

Tutorial: How to Set Up and Trigger a Webhook in Papo Global 1. Introduction to Triggering Webhooks - In this tutorial, we will show how to set up a Webhook that fires automatically when messages are received on the Papo Global platform. This lets you automate replies and specific actions, speeding up customer service. https://www.youtube.com/watch?v=Vgmfx38MR1Y 2. Accessing the Webhook Settings - Log in to the Papo Global platform and go to the Settings section. - Look for the Webhooks area under Integrations. - Click to add a new Webhook and start the setup. 3. Defining the Webhook Trigger - Choose which type of message will trigger the Webhook. The options include: - All messages: the Webhook fires for any message received. - Specific messages: set up filters, such as keywords or other criteria, that trigger the Webhook. - Define the conditions that match your service flow. 4. Configuring the Webhook URL - Enter the destination URL where the message information will be sent. - Configure the parameters to send the required data, such as the message content, sender information and any other details the destination system needs. 5. Testing the Webhook - Once it is set up, run a test to make sure the Webhook works: - Send a message to the configured channel and check whether the Webhook fires correctly. - Verify that the data reaches the destination URL with all the information complete. 6. Monitoring and Adjusting - Monitor the Webhook's performance on the Papo Global platform to make sure it works as expected. - Adjust the settings as needed to optimize triggering and data delivery. Start free on Papo Global → First user $0, no credit card. Learn more at papo.global.

How to Create Your Papo Global Affiliate Account and Generate Trackable Links

youtube This step-by-step guide shows how to create your affiliate account on Papo Global and generate trackable links for your campaigns. The process is quick and simple, so you can start earning commissions in no time. Accessing and Creating Your Account To get started, follow these steps: 1. Open your browser and type chat.papo.global in the address bar. 2. You will be redirected to the platform's login/sign-up page. 3. Choose one of the options: - Continue with Google: the fastest option if you already have a Google account. - Create an account with email and password: fill in your details, such as name, email, phone number and password. After filling in your details or signing in with Google, you will need to verify your email. A verification link is sent to the address you registered. Click this link to be redirected and continue the process. Initial Profile Setup When you click the verification link, you will be taken to a screen to review your details. - Access details: check your name, email and phone number. - Your role: select your role in the company (if applicable). - Company details: - Website: entering a website is required to proceed. You can use any website, but we recommend using a social media profile, such as your Instagram profile. - Language: your language (the video uses Brazilian Portuguese). - Time zone: your time zone (the video uses America/São Paulo). - Company industry and size: select the options that best match your profile. - Where did you find us? Select the source. Once you have filled in all the information, click "Continue". Setting Up Conversation Channels On the next screen, you will see options to set up communication channels such as WhatsApp, Facebook and Instagram. - If you plan to use the platform as a customer, you can connect these channels. - If your goal is to be an affiliate, just click "Skip" to go straight to the main dashboard. Accessing the Affiliate Program Once you are on the main dashboard, you can open the affiliates section: 1. In the left sidebar, click "Affiliates". 2. On the affiliates screen, click "Join the affiliate program". You are now part of the Papo Global affiliate program. Understanding the Affiliate Dashboard The affiliate dashboard offers several options to manage your referrals and commissions: - Overview: shows your main referral link and a summary of visits, sign-ups, conversions and contacts. - Visits: shows who visited your link and which link was opened. - Referrals: lists the people who signed up through your links. - Link campaigns: lets you create custom links for specific campaigns. - To create a new campaign, set a name (e.g. "WhatsApp" or "Instagram") and the destination (usually /app/auth/signup). - When you create the campaign, you get a unique link to track the visits, sign-ups and conversions generated by that specific campaign. - Media: here you can prepare and manage media materials for your promotions. - Payout: connect your Stripe account to receive your commissions automatically. Stripe is a payment system that works with all local banks. - Network: shows information about your affiliate network (if any). - Commissions: details the commission amounts you have received. - Engagement: shows your engagement rate on the platform. Takeaways - Simple Sign-up: create your account easily with email and password or by connecting with Google. - Email Verification: keep your account secure by verifying your registered email. - Website Required: although you need to enter a website, a social media profile such as Instagram works perfectly to get started. - Skip Customer Setup: if your focus is being an affiliate, you can skip connecting channels such as WhatsApp, Facebook and Instagram during the initial setup. - Complete Dashboard: the affiliate dashboard gives you a full view of visits, referrals, campaigns and commissions. - Trackable Links: create custom campaigns with unique links to monitor performance. - Payouts via Stripe: connect your Stripe account to receive commissions automatically and securely, with support for local banks. - Support Available: if you have any questions, Papo Global support is available via chat. Start free on Papo Global → First user $0, no credit card. Learn more at papo.global.

How to Create Your Own Help Center with Papo Global

With Papo Global (https://papo.global/), you can create your own Help Center using the integrated Help Center module. This tool allows you to develop knowledge portals, organize articles into categories, and offer a complete self-service channel for your customers and internal team, reducing the load on your support agents. A well-structured Help Center is essential for scaling customer service. It centralizes important information, tutorials, and answers to common questions, allowing users to find solutions on their own, at any time of day. At Papo Global, this functionality was designed to be simple and directly connected to your support ecosystem. Help Center Components The Help Center structure in Papo Global is organized into three main levels, ensuring that information is easy to find and manage. | Component | Description | Usage Example | | :--- | :--- | :--- | | Portal | This is the main website for your Help Center. You can have one or more portals, for example, one for customers and another for internal training. | help.yourcompany.com | | Category | These are the sections that organize articles within a portal. They function like folders to group content by topic. | "Billing", "Getting Started", "Integrations" | | Article | This is the content page itself, containing text, tutorials, and answers. Each article belongs to a category. | "How to get a duplicate invoice" | Step-by-step to create your Help Center Creating and publishing your knowledge base with Papo Global is a straightforward process. Follow the steps below to set up your self-service portal. 1. Access the Help Center Module In the Papo Global dashboard, locate and access the "Help Center" module. There, you will have an overview of all your portals, categories, and articles. 2. Create Your First Portal The portal is the home of your Help Center. Start by creating a new portal and giving it a clear name, such as "Customer Help Center" or "Internal Knowledge Base". This will be the starting point for all your documentation. 3. Define Categories With the portal created, the next step is to organize the structure. Think about the main topics your customers or team have questions about. Create categories for each of these topics. Good categories help users navigate content intuitively. Examples of categories: - For customers: Getting Started, Payment Questions, Product Guide, Troubleshooting. - For internal team: Sales Processes, Support Scripts, Company Policies, Tool Training. 4. Write and Save Articles as Drafts Within the categories, start creating articles. The platform allows you to write content and save it as a draft. This is useful for preparing material carefully, reviewing, and approving it before making it public. Use clear language, short sentences, and format the text for easy reading. 5. Publish Articles When an article is ready, simply change its status from "draft" to "published". From that moment on, it will be visible to users accessing your Help Center portal. You can update, edit, or remove articles at any time. Who is the Help Center for? The Help Center module is a versatile tool that meets various needs of a growing business. - Companies looking to scale support: Reduce the volume of repetitive tickets by allowing customers to find answers to common questions on their own. - Customer Success Teams: Offer an onboarding and continuous education resource for users, increasing product adoption and satisfaction. - Operations with remote or large teams: Create an internal knowledge base to standardize processes, train new employees, and ensure everyone has quick access to correct information. - Businesses needing 24/7 support: A Help Center functions as an always-on support agent, offering help outside business hours. Frequently Asked Questions Can I have more than one portal in my Help Center? Yes, the platform allows the creation of multiple portals. This is ideal for separating the knowledge base aimed at external customers from the one intended for internal team use, for example. Is the Help Center integrated with Papo's AI? Yes. The articles created in your Help Center can be used as a knowledge source to feed Papo Global's artificial intelligence. This allows the chatbot to provide more accurate and contextualized automatic responses, based on your official documentation. Can my customers search articles? Yes. The search functionality is integrated into the portal, allowing users to type keywords to quickly find the most relevant articles for their questions. How can I organize article content? You can structure content using headings, paragraphs, lists, and tables to make information clear and easy to consume. Good formatting is essential for the reader's experience. Can I create a Help Center just for my team? Absolutely. The module is perfect for creating an internal knowledge base. You can centralize tutorials on tool usage, process guides, company policies, and other important information for your daily operations. Is the Help Center a paid feature? The Help Center module is part of the Papo Global ecosystem of tools. For details on which functionalities are included in each plan, please consult the pricing page on the official website. Read also - Feeding AI: How to Create a Knowledge Base for Automatic Responses - Papo Global dashboard overview: sidebar menu and modules Start for free with Papo Global → The first user is free, and registration does not require a credit card.

How to integrate your Google Calendar to sync your appointments

Yes, you can integrate your Google Calendar account directly with the Papo platform (https://papo.global/) to automate and synchronize your appointments. This integration allows the system to read your real-time availability and automatically create events in your calendar, eliminating the need for manual scheduling and preventing time conflicts. Connecting your Google Calendar to Papo is a fundamental step to automate customer service and optimize your team's time management. This integration transforms how you schedule appointments, allowing Papo's Artificial Intelligence to schedule for you directly in WhatsApp conversations, based on your real availability. | Feature | Description | | :--- | :--- | | Availability Synchronization | Papo reads busy slots in your Google Calendar to know when you or your team are unavailable, preventing the offering of already booked times. | | Automatic Event Creation | When an appointment is confirmed (either by AI on WhatsApp or by an attendant), an event is automatically created in your Google Calendar with the client's details. | | Smart Service | Papo's Artificial Intelligence uses the synchronized calendar to suggest available times to clients during a conversation, completing the entire scheduling process. | | Centralized View | All appointments are visible both in Papo's Service module and in your Google Calendar, keeping organization in one place. | How Google Calendar Integration Works The integration functions as a two-way bridge between Papo and your Google account. 1. Availability Reading: Once connected, Papo starts checking your Google Calendar in real-time. If you have a personal meeting or any other scheduled commitment, the system understands that time slot is unavailable and will not offer it to a client trying to book a service. 2. Event Creation: When a client requests an appointment via WhatsApp, Papo's AI springs into action. It consults available times (considering existing commitments in your Google Calendar and the work schedule configured in the Service module), offers the available options, and, after client confirmation, creates the event directly in your Google Calendar. This process eliminates the manual "copy and paste" work between chat and calendar, reducing human errors and ensuring no appointment is lost or double-booked. Step-by-Step Guide to Connecting Your Google Calendar Setting up the integration is a simple process. Although the exact location may vary slightly depending on platform updates, the general flow is as follows: 1. Access Integration Settings: Within the Papo platform, navigate to the settings area. The option to connect the calendar is usually located in the Service module or a general Integrations section in your profile or account settings. 2. Locate the Google Calendar Option: Look for the icon or the "Google Agenda" or "Google Calendar" option and click to start the connection process. 3. Connect Your Google Account: You will be redirected to a Google login screen. Enter the email and password for the Google account you wish to synchronize with Papo. This can be a personal account (@gmail.com) or a professional Google Workspace account. 4. Authorize Permissions: Google will ask you to authorize Papo to access and manage your calendar. It is crucial to grant these permissions. The platform needs them to read your busy times and to create new events on your behalf. Papo uses these permissions strictly for scheduling functionality. 5. Check Connection Status: After authorization, you will be redirected back to the Papo platform. The integration section should now show a "Connected" status, indicating that synchronization is active. With the connection established, your calendar is ready to be intelligently managed by Papo. Who is this integration for? This functionality is especially valuable for any business that operates based on appointments and wants to optimize the process, freeing up the team from repetitive tasks. Some examples include: - Clinics and Offices: Doctors, dentists, psychologists, and physical therapists who need to manage patient schedules. - Beauty Salons and Barbershops: Professionals who schedule haircuts, treatments, and other aesthetic services. - Law and Accounting Firms: For scheduling meetings, consultations, and client appointments. - Service Providers: Technicians, consultants, and instructors who conduct visits or scheduled sessions. - Pet Shops and Veterinary Clinics: For scheduling consultations, baths, grooming, and other animal care. Frequently Asked Questions (FAQ) Does the integration work with any Google account? Yes, the integration is compatible with both personal Google accounts (@gmail.com) and professional Google Workspace accounts (your-email@yourcompany.com). What happens if I already have a personal commitment in my calendar? Papo will identify it as a busy slot and will not offer that time to clients. The integration respects all existing events in your calendar, ensuring your privacy and avoiding conflicts between personal and professional commitments. Can I connect more than one Google Calendar to my Papo account? The rules for connecting multiple calendars may vary depending on your plan and account settings. For specific details on how to manage calendars for multiple professionals, please consult your account settings or the official documentation on the website. Does Papo's AI really schedule appointments in my calendar automatically? Yes. After setup and integration with Google Calendar, Papo's Artificial Intelligence can manage the entire scheduling flow: understand the client's request in chat, check real-time availability, propose times, and, upon confirmation, create the event in your Google Calendar without human intervention. Do I need the Service module to use the integration? Yes, the Google Calendar integration is a core feature of Papo's Service module. It is in this module that you register your services, define their duration, and assign responsible professionals – information that the AI uses to make correct appointments. How does Papo know the duration of each service to block the calendar? The duration of each service is defined by you when you register it in the Service module. When a client schedules a "Haircut" for 1 hour, for example, the system automatically blocks a 1-hour period in the corresponding professional's calendar. Read also - How to use the Service module to schedule services and appointments Start using for free → The first user is free and allows you to test the platform's main features.

How to Manage Documents in Papo's File Center

Papo's File Center (https://papo.global/) is the centralized repository where you can upload, organize into folders, and manage all your company's important documents. This feature ensures that your files, such as contracts, manuals, and spreadsheets, are always accessible and ready to be used across the platform, especially to feed the knowledge base of your artificial intelligence assistants. Document management is essential for maintaining the organization and efficiency of any operation. With the File Center, you eliminate the need to search for files in WhatsApp conversations, emails, or local drives, centralizing everything in a single, secure location integrated into your customer service and CRM environment. | Feature | Description | | :--- | :--- | | File Upload | Upload documents, spreadsheets, images, PDFs, and other file formats directly to your Papo account. | | Folder Organization | Create a structure of folders and subfolders to categorize files by department, document type, or project. | | Centralized Search | Find files quickly by searching by name, folder, or usage context within the platform. | | AI Integration | Use documents as a knowledge source to train AI assistants, such as Capitão, to answer questions automatically. | | Unified Access | Make files available to the entire team, ensuring everyone always uses the most up-to-date versions of proposals, catalogs, and manuals. | How the File Center Works The File Center functions as a corporate cloud drive, but fully integrated with Papo's modules. Instead of just being a storage location, it connects your documents to the tools your team uses daily. For example, a product manual in PDF that is in the File Center can be linked to the Capitão AI assistant. When a customer asks a question about the product in chat, the AI can consult the document to provide an accurate and instant answer, without the need for human intervention. Similarly, a standardized commercial proposal can be stored and easily attached in a conversation with a lead, streamlining the sales process and ensuring consistency in communication. Step-by-Step Guide to Managing Your Files Although the exact interface may vary, the process for managing your documents in Papo follows a simple and intuitive logic. 1. Access the File Center: Typically, you will find access to the File Center in the platform's main menu or within your account settings, in an area dedicated to resource management. 2. Upload Files: Inside the File Center, look for the "Upload" or "Send File" option. You can select one or more files from your computer to add to the platform. It is possible to upload them to the root folder or directly to a specific folder you have already created. 3. Create and Organize Folders: To keep everything organized, create a folder structure that makes sense for your operation. For example: "Contracts", "Commercial Proposals", "Training Manuals", and "Marketing Material". The platform allows you to view folders and the number of files within each, facilitating navigation. 4. Search and Use Files: Use the search bar to locate a document by name or by the folder where it is stored. Once you find the file, you can view it, get its link, or associate it with other functionalities, such as an AI assistant's knowledge base. Empowering AI with Your Documents The main advantage of the File Center is its native integration with Papo's AI assistants, such as Capitão. By using your own documents as a knowledge source, you ensure that the AI responds with accurate information aligned with your company. The process is straightforward: 1. Upload relevant documents (FAQs, manuals, policies, etc.) to the File Center. 2. Access the settings of your Capitão assistant. 3. Link the desired documents to the assistant's knowledge base. From this moment on, the AI will be able to consult the content of these files to answer customer questions and even assist your agents during service, suggesting answers based on official documentation. Frequently Asked Questions (FAQ) What types of files can I upload to the File Center? You can upload the most common file formats used in office environments, such as PDF, DOCX, XLSX, TXT, JPG, and PNG. For information on specific file size limits or types, please consult the documentation within the platform itself. How are files used by artificial intelligence? The documents you choose to link to an AI assistant, such as Capitão, become part of its knowledge base. The AI analyzes the content of these files to formulate accurate answers to customer and agent questions, automating support based on your official sources. Is it possible to organize files into folders? Yes. The File Center is designed to allow the creation of a hierarchical folder structure, just as you would on your computer. This helps keep documents categorized and easy to find. How do I find a specific file? The platform offers a search functionality that allows you to search for files by name, by the folder they are located in, or by the context in which they are used, such as which files are associated with a particular AI assistant. Are my files secure on the platform? Yes. Papo Global is a professional SaaS platform that operates with secure infrastructure to protect customer data and documents. Your files are stored securely and are accessible only by authorized users of your account. Read also - Feeding AI: How to Create a Knowledge Base for Automatic Responses - Overview of the Papo Global dashboard: side menu and modules Start for free and organize your documents → The first user is free and allows you to centralize your files and conversations in one place.

How to Integrate Wavoip to Make and Receive Calls in Papo

To integrate Wavoip and start making and receiving calls directly through the Papo platform (https://papo.global/), you need to create a new inbox, select the voice channel corresponding to Wavoip, and configure it with your API token. This integration allows you to centralize voice calls in the same panel where you manage WhatsApp and other channels, unifying the customer service history. Integrating your Wavoip telephony account with Papo transforms how your team handles voice calls. Instead of using a physical phone or a separate softphone, agents can make and receive calls directly from the Papo interface, where they already have the full customer context, including previous chat and email conversations. Integration Summary The connection process is done in a few steps and requires administrator access to both your Papo account and your Wavoip account. | Step | Action | |---|---| | 1. Get Token | Access your Wavoip account and copy the API token required for the integration. | | 2. Create Inbox | In Papo, go to Settings → Inboxes and click "Add inbox". | | 3. Select Channel | Choose the voice channel and select "Wavoip" as the provider. | | 4. Configure | Name the inbox (e.g., "Sales - Voice"), paste the Wavoip token, and save. | | 5. Add Agents | Assign agents or teams who will be able to use this inbox to make and receive calls. | Step-by-Step Guide to Integrating Your Wavoip Account Follow the steps below to connect your Wavoip telephony service to your Papo inbox. 1. Obtain Your API Token from Wavoip Before starting the configuration in Papo, you need your Wavoip authentication token. 1. Access the administration panel of your Wavoip account. 2. Navigate to the API or integrations section to find your token. 3. Copy the token. It will be used in the next step. If you have difficulty finding the token, consult Wavoip's help documentation or contact their support. 2. Create the Inbox in Papo With the token in hand, the next step is to create the communication channel within Papo. 1. Access your Papo account and go to Settings in the sidebar menu. 2. Click on Inboxes. 3. Press the Add inbox button. 4. In the list of available channels, select the Voice option, and then choose Wavoip as the provider. 5. Fill in the configuration form: - Inbox Name: Give it a name that helps identify the channel, such as "Voice Support" or "Sales - Calls". - Wavoip Token: Paste the token you copied in the previous step. 6. Click on Create Inbox to save. 3. Assign Agents to the Inbox For your team to be able to answer and make calls, you need to associate agents with the new inbox. 1. After creating the inbox, you will be directed to the Agents tab. 2. Select the agents or teams who will have permission to use this voice channel. 3. Save the changes. From this moment, the integration is active. Calls received on your Wavoip number will be directed to the selected agents within Papo. How It Works in Practice With the integration active, call management is fully centralized. - Receiving Calls: When a customer calls your Wavoip number, a real-time notification will appear on the screen of the agents assigned to that inbox. The agent can accept the call with one click and converse using their computer's microphone and audio. - Making Calls: To initiate a call, the agent can navigate to a contact's profile in Papo's CRM and click the phone icon next to the customer's number. The call will be initiated through Wavoip, but the control interface will remain within Papo. - Unified History: All calls, both received and made, are recorded in the contact's history. This allows any agent, when assisting the same customer in the future, to see the call log along with WhatsApp conversations, emails, and internal notes. Frequently Asked Questions Do I need an active Wavoip account to integrate? Yes, the integration connects your existing Wavoip account to Papo. You need to have an active plan with Wavoip to obtain the API token and for the telephony service to function. Where do I find the Wavoip API token? The API token is provided by Wavoip in their administration panel. Generally, it is found in a section called "API", "Integrations", or "Credentials". For the exact location, consult Wavoip's documentation. Are calls made and received through Papo recorded? Papo records the history of all calls, including date, time, duration, and the agent involved. Audio recording of the call depends on the settings and plan you have with Wavoip. Check your voice provider's functionalities. How does an agent know they are receiving a call? The agent receives a real-time audio and visual notification in the Papo interface, allowing them to answer the call directly in the panel without needing another application. Can I direct calls to specific teams? Yes. When configuring the Wavoip inbox, you can assign it to a specific team created in Papo. This way, only agents who are part of that team will receive call notifications for that inbox. Does the integration incur any extra cost in Papo? The integration functionality with voice providers is part of the Papo platform. Costs associated with using the telephony service, such as per-minute rates and number rental, are charged directly by Wavoip, according to the plan you contracted with them. Read also: - How to Analyze Call History and Statistics in Papo - How to Create Teams and Distribute Service in Papo Global Get started for free with Papo → The first user is free, and no credit card is required for registration.

What is Papo's API and What is it For?

Papo's API (https://papo.global/) is a programming interface that allows developers to connect other systems, such as CRMs, ERPs, or automation platforms (like n8n), directly to their Papo account. It serves to automate actions, such as sending WhatsApp messages, querying Extractor contacts, or triggering the platform's artificial intelligence, without needing to use the graphical interface. The API opens up a range of possibilities to customize and scale your operation, integrating Papo's functionalities into your company's existing workflows. Instead of performing actions manually in the dashboard, your own software can command Papo to execute tasks. API, Webhooks, and Ready-Made Integrations: What's the Difference? It's common to confuse these three concepts. The table below summarizes the main difference between them and when to use each. | Characteristic | API (Application Programming Interface) | Webhooks | Ready-Made Integrations | | :--- | :--- | :--- | :--- | | Direction | Your system requests or sends data to Papo. | Papo sends data to your system. | Papo connects to another service. | | Action Initiative | Your external system. | The Papo platform. | The user, when configuring in the dashboard. | | Technical Knowledge | Requires programming or the use of tools like n8n. | Requires an endpoint (URL) in your system to receive data. | Does not require programming, only configuration in the dashboard. | | Example of Use | Send a WhatsApp message when a purchase is approved in your e-commerce. | Notify your billing system whenever a new contact is created in Papo. | Connect your Google Calendar account so Papo's AI can schedule meetings. | What is Papo's API Used For? With the API, you can build custom automations and integrations for your business. Some of the main applications include: - Send Messages: Initiate conversations or send WhatsApp notifications from your own system (e.g., order confirmation, payment reminder). - Access Extractor Contacts: Query the list of leads generated by Papo's Extractor and import them into your CRM or marketing tool. - Manage Instances: Check the status of your WhatsApp connections directly from your backend. - Utilize Artificial Intelligence: Send text to the AI API and receive a generated response based on the prompt configured in your Papo account, allowing you to use the same intelligence in other contexts. - Synchronize Data: Keep your contacts, companies, and deals synchronized between Papo and your main CRM. - Create Custom Dashboards: Extract service and performance data to feed Business Intelligence (BI) dashboards with specific metrics for your operation. How to Start Using the API To use the API, you need technical knowledge or to use a visual automation tool that supports REST API calls, such as n8n. The general process is simple: | Step | Action | Details | | :--- | :--- | :--- | | 1. Generate API Keys | Access the Papo dashboard and go to the developer section to create your keys. | You will have a public key (pk_live_...) to identify your account and a secret key (sk_live_...) for authentication. The secret key is displayed only once. | | 2. Consult the Documentation | Visit the official API documentation to see all available endpoints. | The documentation details the URLs, required parameters, and response formats for each action (send message, list contacts, etc.). | | 3. Implement the Calls | Write the code in your system or configure the blocks in your automation tool. | Calls are made via HTTPS to the base URL https://app.papo.global/api/v1, sending the secret key in the authorization header. | | 4. Test the Integration | Perform tests to ensure your system is communicating correctly with Papo. | Verify that messages are sent and data is received as expected. | Frequently Asked Questions Do I need to be a programmer to use the API? Yes, direct use of the API requires programming knowledge. However, automation tools like n8n or Make allow you to connect to the API through a visual interface, without needing to write code, by simply configuring action blocks and entering your keys. Where can I find my API keys? API keys can be generated in your Papo account's settings dashboard, in a section dedicated to developers. Remember that the secret key is shown only at the time of its creation. Store it in a secure location, as it cannot be recovered. If lost, you will need to revoke it and create a new one. What exactly can I do with the API? You can perform various actions that you would manually do on the platform. The official documentation lists all endpoints, but the main ones are: sending text messages via WhatsApp (/messages), listing extracted contacts (/contacts), listing your WhatsApp connections (/instances), and using Papo's AI engine to generate texts (/ai/v1/complete). Does using the API incur additional costs? Access to the API itself does not incur additional costs on your plan. However, the actions you perform through it may consume resources that are charged, such as sending messages via the WhatsApp API or extracting new leads with the Extractor. For details on operational costs, consult the pricing page on the Papo website. Is Papo's API REST or SOAP? Papo's API is a modern REST API. It uses standard HTTP methods (GET, POST, etc.) and communicates using the JSON format, which is lightweight and easy to interpret by most programming languages and automation tools. What's the difference between using the API directly and using a ready-made integration like Google Calendar? The API offers full flexibility for you to create any type of integration. Ready-made integrations, such as Google Calendar or Wavoip, are pre-built solutions by Papo for common use cases. They are activated with a few clicks, without needing code, but are limited to the functionalities that have been previously developed. Read also - How to Integrate Wavoip to Make and Receive Calls in Papo - Creating Your First Automation Flow from Scratch Start for free and explore the possibilities → Connect your channels, configure AI, and start serving customers on the same day.

How to Manage Your Subscription, Invoices, and Credits in Papo

To manage your subscription, invoices, and credits in Papo (https://papo.global), access the payments section within your account settings. There, you will find a link to the payment portal, where you can view your current plan, download past invoices, update your payment method, and add credits for pay-per-use services, such as WhatsApp campaigns. Keeping track of the administrative side of your account is essential to ensure your customer service and sales operations run smoothly. Papo centralizes financial management in a secure payment portal, allowing you to manage your subscription and credits autonomously and transparently. Financial Management Summary in Papo The table below summarizes the main account management actions and where to perform them. | Action | Where to Perform | Description | | --- | --- | --- | | View Current Plan | In the payments section of the Papo dashboard and in the payment portal. | Check your subscription details, such as the number of agents included and the recurring amount. | | Download Invoices | In the payment portal. | Access your billing history and download invoices for your financial records. | | Change Payment Method | In the payment portal. | Update your credit card details or other registered payment method. | | Add Credits | In the payments section of the Papo dashboard. | Recharge your credit balance to use for specific features, such as bulk messaging. | How to access your payment portal The payment portal is a secure area, provided by our payment processing partner (Stripe), where you can manage all aspects of your subscription. Follow these steps to access it: 1. Log in to your Papo Global account. 2. Navigate to the Settings area of your account. 3. Look for the option related to Payments, Subscription, or Billing. 4. Within this section, you will find a summary of your current plan and a button or link to "Manage Subscription" or "Access Payment Portal". 5. Upon clicking, you will be securely redirected to the portal, where you can perform the necessary actions. Managing your subscription and plans Within the payments section of the Papo dashboard, you can see a clear summary of your current plan. This includes the plan name, amount, next renewal date, and the number of contracted users (agents). If you need more agents or features, the platform will display available billing plans for an upgrade. Plan changes are made directly through the payment portal, ensuring a simple and secure transition. Remember that the first user in Papo is free and does not require a credit card, but adding new team members activates billing for a paid plan. How to download your invoices Keeping a record of your expenses is essential for your company's accounting. The payment portal stores your entire billing history. To download an invoice: 1. Access the payment portal as per the instructions above. 2. Look for the "Billing History" or "Invoices" section. 3. You will see a list of all past charges, with date and amount. 4. Click on the desired invoice to view it in detail or to download the document in PDF format. Adding and using credits In addition to your monthly or annual subscription, which covers platform access and a defined number of agents, some features operate based on pre-paid credits. A common example is using the Sender module to send bulk message campaigns via WhatsApp. How it works: - Subscription: Ensures continuous access to the platform for your team. - Credits: Are a balance you purchase separately and are consumed as you use specific services. To add credits: 1. Access the Payments section in your Papo dashboard. 2. Look for the "Add Credits" or "Recharge Balance" option. 3. You will be directed to a checkout page, where you can choose the top-up amount and complete the payment. 4. The credit balance will be updated in your account and will be visible on the dashboard. This separation ensures that you only pay for what you use in volume services, keeping your subscription cost predictable. Frequently Asked Questions How can I change my plan? To change your plan, access the payments section in the Papo dashboard. There, you will be able to see the available plans and will be directed to the payment portal to confirm the change. The change is usually immediate, and billing will be adjusted in the next billing cycle. What is the difference between subscription and credits? The subscription is a recurring payment (monthly or annually) that grants access to the Papo platform, including a specific number of agents and access to core modules. Credits are a pre-paid balance used for consumption-based features, such as sending bulk WhatsApp campaigns, calls, or advanced API usage. Where can I find my payment history and invoices? All your payment history and downloadable invoices are available in the payment portal. To access it, go to the billing section in the Papo dashboard and click on the subscription management link. What payment methods are accepted? Accepted payment methods, such as credit card and other options, are displayed directly in the payment portal when you sign up or update your plan. What happens if my subscription payment fails? If a payment fails, you will usually receive an email notification. It is important to update your payment method in the portal as soon as possible to avoid service interruption. Access to the platform may be suspended after a period of non-payment. Read also - How much does Papo Global cost? Plans, prices, and free plan - How to add agents (attendants) to your Papo Global account Start for free with Papo → The first user is free, and no credit card is required for registration.

How to Generate and Use API Keys to Integrate with Other Systems

To integrate your account with external systems like CRMs, ERPs, or automation platforms (n8n, Zapier), Papo (https://papo.global/) offers API (Application Programming Interface) keys that can be generated and managed directly in your dashboard. These keys function as secure credentials that authorize other software to programmatically access and perform actions in your Papo account. Papo's API allows you to build connected work ecosystems, automating tasks ranging from sending WhatsApp messages to extracting qualified leads. To ensure security, Papo uses a two-key system: a public key for identification, and a secret key for authentication. | Key Type | Description | Security Level | Example Usage | | :--- | :--- | :--- | :--- | | Public Key (pk_live_...) | A unique and fixed identifier for your Papo account. | Low. Can be exposed publicly. | Identify your account in a script on your website's frontend. | | Secret Key (sk_live_...) | An API "password". Authenticates your requests and grants permission to act on behalf of your account. | High. Must be kept strictly confidential. | Authenticate an API call from your server (backend) to send a message. | How to Generate and Find Your API Keys API keys are managed in a specific area of your Papo account. Follow the steps below to access them. 1. Access your Papo dashboard and navigate to Settings. 2. In the settings menu, look for the Developers or API section. 3. On this page, you will find your Public Key (pk_live_...), which is fixed and can be copied at any time. 4. For the Secret Key, you will need to generate a new one. Click the button to create a new key. 5. Give the key a descriptive name, indicating where it will be used (e.g., "CRM Integration", "N8N Automation"). This helps identify and revoke specific keys if necessary. 6. After creation, the Secret Key (sk_live_...) will be displayed only once. Copy it and store it in a secure location, such as a password manager or an environment variable on your server. For security reasons, Papo does not store the original key value and cannot display it again. If you lose a secret key or suspect it has been leaked, revoke it immediately in the dashboard and create a new one. How to Use the Keys to Authenticate with the API All communication with Papo's API that involves actions or access to private data must be authenticated. This is done by sending the secret key in an HTTP header. The base URL for all API calls is: https://app.papo.global/api/v1 To authenticate, include your secret key in the Authorization header of your request, preceded by the word Bearer. Example curl request to get your account data: curl https://app.papo.global/api/v1/me \ -H "Authorization: Bearer YOUR_SECRET_KEY_HERE" In this example: - sk_live_YOUR_SECRET_KEY_HERE must be replaced with your actual secret key. - The /me endpoint returns information about the authenticated account, serving as a good test to verify if your key is working. The public key (pk_live_...) can optionally be sent in the X-Papo-Public-Key header as an additional verification, but the primary authentication is always done by the secret key. What Can You Do with Papo's API? The API opens up a range of possibilities for automating and integrating your operations. Here are some examples of what you can do: - Send WhatsApp messages: Create scripts to send notifications, alerts, or transactional messages through one of your connected numbers. - Fetch contacts from the Extractor: Access the list of leads you extracted with the CNPJ Extractor to synchronize them with your main CRM. - Manage instances: List and check the status of your WhatsApp connections. - Use Artificial Intelligence: Send texts to Papo's AI engine and receive generated responses based on your configured prompts. - Synchronize data: Keep your internal systems (ERP, BI) updated with the data generated in Papo. Frequently Asked Questions (FAQ) Where can I find the complete API documentation? Detailed technical documentation, with all endpoints, parameters, and code examples in different languages (JavaScript, Python), is publicly available at papo.global/pt/docs. My secret key was leaked. What should I do? If you suspect your secret key has been compromised, immediately access the developers area in your Papo dashboard, find the leaked key in the list, and click to revoke it. Once revoked, it can no longer be used to authenticate requests. Then, generate a new key to replace the old one in your integrations. How many secret keys can I create? You can create multiple secret keys. It is good security practice to generate a different key for each system or environment you integrate (e.g., one for your CRM, another for your automation system, one for the testing environment, etc.). This allows you to revoke access for a specific system without affecting the others. Can I use the public key on my website's frontend? Yes, the public key (pk_live_...) is designed to be safe for use in public environments, such as your website's JavaScript code. Its function is only to identify your account, not to authenticate actions. The secret key, on the other hand, should never be exposed in client-side code. What's the difference between Papo's API and a Webhook? The main difference lies in who initiates the communication. With the API, your system initiates the action: you "request" (pull) data from Papo or "tell" (push) Papo to do something, like send a message. With a Webhook, Papo initiates the action: it "pushes" data to your system automatically when a specific event occurs (e.g., a contact reaches a stage in a Flow). What's the difference between Papo's API and the Official WhatsApp API? The Official WhatsApp API focuses exclusively on WhatsApp channel functionalities. Papo's API is a broader and more powerful abstraction layer: it allows you to control not only WhatsApp but also other platform modules, such as the CRM, the Lead Extractor, and the Artificial Intelligence engine, all with a single set of keys and in a simplified way. Read also - How to use the Webhook action in Automation Flows to integrate with other systems - Can I use the same WhatsApp Business App number with Papo's Official API? Start integrating for free → The first user is free for you to test automations and integrations with your number.

How to connect Telegram to centralize customer service

To connect Telegram and centralize customer service, you must first create a bot on Telegram using BotFather to obtain an API token. Then, on the Papo platform (https://papo.global/), you need to add a new inbox, select the "Telegram" channel, paste your bot's token, and associate your team's agents to start managing all conversations in a unified dashboard. Integrating Telegram with Papo allows your team to respond to and manage customer interactions directly within the omnichannel inbox, alongside other channels like WhatsApp, Instagram, and Email. This eliminates the need to switch between applications, ensures a unified history, and enables the use of Papo's automation and reporting tools to optimize your Telegram customer service. The table below summarizes the connection process: | Step | Action | Details | | :--- | :--- | :--- | | 1 | Create a Telegram bot | Use @BotFather on Telegram to create a new bot and get the access token. | | 2 | Access Inboxes in Papo | In the side menu, go to Settings → Inboxes. | | 3 | Add a New Inbox | Click on Add inbox and choose the Telegram channel. | | 4 | Enter the Bot Token | Paste the token provided by BotFather into the designated field. | | 5 | Configure and Activate | Give the inbox a name and associate the agents who will handle the service. | | 6 | Test the Connection | Send a message to your bot on Telegram and check if it arrives in Papo. | Step-by-step guide to connect your Telegram bot Follow the detailed steps below to set up your Telegram channel in Papo. The process is divided into two parts: creating the bot on Telegram and connecting it to Papo. Part 1: Creating your Telegram bot with BotFather Before connecting to Papo, you need to have a Telegram bot. If you already have one, you can skip to Part 2. 1. Start a conversation with BotFather: Open the Telegram app, search for @BotFather (look for the verified profile), and start a conversation with it. BotFather is the official Telegram bot for managing all other bots. 2. Create a new bot: Type or click the /newbot command. 3. Name your bot: BotFather will ask for a name for your bot. This is the name your customers will see. Example: "XYZ Store Support". 4. Choose a username: Next, choose a username for the bot. It must be unique and end with the word "bot". Example: XYZStoreSupport_bot. 5. Copy the access token: If the username is available, BotFather will send a confirmation message containing the access token (API token). This token is a long string of characters and numbers. Copy it and keep it in a safe place, as you will need it in the next step. Part 2: Setting up the inbox in Papo With the token in hand, the process in Papo is simple and quick. 1. Access Inbox Settings: Log in to your Papo dashboard. In the left sidebar menu, click the Settings icon, then select the Inboxes option. 2. Add a New Inbox: On the "Inboxes" screen, click the Add inbox button. You will see a list of all channels that can be integrated with Papo. 3. Choose the Telegram Channel: Select the Telegram option from the list. 4. Paste the Bot Token: In the configuration form, paste the access token you copied from BotFather into the "Bot Token" field. 5. Finalize the Configuration: - Inbox Name: Give it a descriptive name for easy identification (e.g., "Support - Telegram" or "Sales Telegram"). - Add Agents: Associate the members of your team who will be responsible for handling conversations that arrive through this channel. Only agents added here will be able to view and respond to messages in this inbox. 6. Create the Inbox: Click on Create Inbox. Papo will automatically configure the connection (webhook) with Telegram. Done! Your new Telegram inbox will appear in the list of channels. To test, search for your bot by username on Telegram, send a message, and watch it appear instantly in your Papo dashboard. Frequently Asked Questions Do I need technical knowledge to create a Telegram bot? No. The process of creating a basic bot for customer service is done through a conversation with @BotFather on Telegram, following simple commands. You don't need to write any code to obtain the token required for integration with Papo. What is a bot "token" and why is it important? The token is a unique authorization key, like a password, that allows the Papo platform to securely communicate with the Telegram API on behalf of your bot. It is crucial that you keep your token secret and do not share it publicly. If you believe your token has been compromised, you can generate a new one through BotFather using the /revoke command. Can I connect more than one Telegram bot to Papo? Yes, you can connect multiple Telegram bots, each in its own inbox. This is useful for managing different departments or brands. The number of inboxes you can create depends on your Papo plan limits. Will old Telegram messages appear in Papo after connection? No. The integration will start synchronizing new messages that arrive at your bot from the moment the connection is successfully established. Previous conversations and messages will not be imported into the Papo platform. What to do if messages are not arriving in Papo? If messages sent to your bot do not appear in your Papo inbox, check the following points: 1. Correct Token: Confirm that the token pasted into Papo is exactly the same as provided by BotFather and that it has not been revoked. 2. Associated Agents: Check if at least one agent (even if it's you) has been added to the Telegram inbox in Papo's settings. Without agents, conversations have nowhere to be directed. 3. Channel Status: In the "Inboxes" section of Papo, verify that the Telegram channel appears as active. Start using for free and centralize your customer service → The first user is always free for you to test and organize your channels.

How to Save Papo Leads to Google Sheets with Webhooks

To save new leads and deals from Papo (https://papo.global/) directly to a Google Sheets spreadsheet, you can use the Flows automation module to set up a trigger that, when activated, sends contact data via a Webhook action. This requires creating an endpoint (URL) in Google Sheets, either through an automation platform like Zapier or Make.com, or with a Google Apps Script, to receive the information sent by Papo in real-time. Connecting Papo to Google Sheets allows you to create a centralized, automatically updated lead database, without the need to manually export and import spreadsheets. This integration is ideal for sales, marketing, and operations teams that need visibility into generated contacts and their progress in the funnel. Integration Process Overview The automation acts as a bridge between Papo and Google Sheets. When a specific event occurs in Papo (such as the creation of a new contact), the Flow is triggered and sends the data to the URL you configured. | Step | Tool | Action | | :--- | :--- | :--- | | 1. Preparation | Google Sheets & External Tool | Create the spreadsheet that will receive the data and generate a Webhook URL using a service like Zapier/Make.com or a Google Apps Script. | | 2. Trigger | Papo | An event happens on the platform, such as a new contact being created, a tag being added, or a deal being moved in the Kanban. | | 3. Automation | Papo (Flows) | The automation Flow detects the trigger and initiates the configured actions. | | 4. Data Sending | Papo (Webhook Action) | The Webhook action sends a data package (JSON payload) to the URL generated in Step 1. | | 5. Receiving and Recording| Google Sheets | The URL receives the data, and the configured logic (in Zapier or Apps Script) inserts a new row into the spreadsheet with the lead's information. | How to Set Up the Integration Step-by-Step The process is divided into two main parts: first, preparing Google Sheets to receive the data, and second, configuring the automation in Papo to send it. Part 1: Obtain the Webhook URL in Google Sheets Papo needs an address (URL) to send the information to. You don't create this URL in Papo, but rather in the tool that will receive the data. There are two main approaches: Option A: Use an Automation Platform (Recommended for beginners) Tools like Zapier, Make.com (formerly Integromat), or n8n are the easiest ways to connect Papo to hundreds of other applications without code. 1. Create an account on one of these platforms. 2. Start a new automation (a "Zap" in Zapier or "Scenario" in Make). 3. Choose "Webhooks" as the trigger. Usually, the option is called "Catch Hook" or "Custom Webhook". 4. Copy the Webhook URL provided by the platform. It will be unique to your automation. 5. Add an action to the automation to "Add a Row" in Google Sheets. Connect your Google account, select the spreadsheet, and the columns where the data will be saved. Leave this automation active and ready for a test. Option B: Use Google Apps Script (Advanced) If you are familiar with programming, you can create your own endpoint directly in Google Sheets. 1. Open your Google Sheets spreadsheet. 2. Go to Extensions > Apps Script. 3. Paste code with a doPost(e) function that interprets the received data and adds it to the spreadsheet. 4. Click Deploy > New deployment. 5. Select "Web app" type. 6. Configure access to "Anyone" (even anonymous), as the Papo webhook will not log into your Google account. 7. Copy the Web app URL generated. This is your webhook URL. Part 2: Configure the Automation Flow in Papo With the webhook URL in hand, you can now configure Papo to send the data. 1. In the Papo dashboard, access the Flows module. 2. Click to create a new Flow. 3. Define the Trigger: Choose the event that will start the automation. Common examples include: - Contact Created: To save every new lead that enters the platform. - Tag Added: When a lead is qualified and receives a tag like "Hot Lead". - Deal Created: When a card is created in your Kanban funnel. 4. Add the Webhook Action: In the Flow editor, add a new step and select the "Webhook" action. 5. Configure the Action: - URL: Paste the URL you generated in Part 1 (from Zapier, Make, or your Apps Script). - Method: Keep as POST. - Body: Here you define which data will be sent. The format is JSON. You can use Papo variables to dynamically fill in the values. Example JSON body: { "nome": "{{contact.name}}", "telefone": "{{contact.phone}}", "email": "{{contact.email}}", "etapa_funil": "{{deal.stage.name}}", "origem": "{{contact.channel.name}}" } 6. Activate the Flow: Save and activate your automation. From now on, whenever the trigger is activated in Papo, the contact or deal data will be instantly sent to your Google Sheets spreadsheet. Frequently Asked Questions (FAQ) Do I need to know how to code to set up this integration? Not necessarily. Using automation platforms like Zapier or Make.com, you can connect Papo to Google Sheets through a visual interface, without writing any lines of code. The Google Apps Script option is recommended only for advanced users. What kind of data can Papo send via webhook? You can send almost any data associated with the contact, deal, or message, including standard fields (name, phone, email), custom attributes you have created, Kanban funnel information (deal name, value, stage), tags, and conversation details. Does the integration work in real-time? Yes. The Webhook action is executed instantly as soon as the Flow trigger is activated in Papo. This means your leads will appear in the spreadsheet seconds after being created or updated on the platform. Can I update an existing row in Google Sheets instead of creating a new one? Yes, but the logic for this needs to be configured in the tool that receives the webhook (Zapier, Make.com, or your script). For example, in Zapier, you can add a "Lookup Spreadsheet Row" step to check if the lead already exists (by phone or email) and then use an "Update Spreadsheet Row" action instead of "Create Spreadsheet Row". Where can I find the list of variables I can use in the webhook body? Within the Papo Flow editor, when configuring the Webhook action, the platform usually offers a list of available variables ({{contact.name}}, {{deal.value}}, etc.) that you can insert into the JSON body. Start automating your leads for free → Create your Papo account to centralize your communication channels and automate sales and marketing processes.

How to Organize Your Help Center with Categories and Articles

To organize your Help Center in Papo (https://papo.global/), you must first create categories to group topics and then add, edit, and publish articles within those categories. Papo's Help Center module allows you to structure your knowledge base hierarchically, making navigation easier for customers and your internal team. A well-organized Help Center is a powerful tool for scaling self-service, reducing the volume of repetitive inquiries, and ensuring that correct information is always accessible. By structuring content logically, you improve the user experience and optimize your support team's time, allowing them to focus on more complex issues. The Help Center Structure in Papo Content organization in Papo's Help Center module follows a simple three-level hierarchy. Understanding this structure is the first step to planning your knowledge base. | Component | Description | Purpose | | :--- | :--- | :--- | | Portal | The main website that hosts your entire Help Center. You can have multiple portals for different audiences. | To serve as the central access point for all your help content (e.g., help.yourcompany.com). | | Category | Sections or folders that group articles by topic within a portal. | To organize content logically so users can easily find what they are looking for (e.g., "Payments", "Getting Started"). | | Article | The individual content page, containing text, tutorials, images, and answers to specific questions. | To provide detailed information users need to solve a problem or understand a process. | How to Create and Manage Categories Categories are the backbone of your Help Center. Good categorization makes navigation intuitive and finding information much faster. 1. Access the Help Center Module: In the main Papo dashboard, navigate to the "Help Center" module. 2. Select the Portal: If you have more than one portal, choose the one where you want to create the new category. 3. Create the Category: Look for the option to add a new category. Give it a clear and objective name, thinking about how your users would search for that topic. 4. Plan Your Structure: Before creating multiple categories, think about the broad themes of your business. Good categories can be based on: - Customer Journey: Getting Started, Advanced Settings, Troubleshooting. - Product Areas: Sales Module, Support Module, Integrations. - Internal Processes: HR Policies, Service Scripts, Tool Guides. Keeping category names short and direct helps users quickly identify relevant content groupings for their questions. How to Create and Manage Articles With categories defined, the next step is to populate the knowledge. Articles are the pages that contain the answers and guides your users will consume. The lifecycle of an article in Papo is designed to allow collaboration and quality control before publication. 1. Navigate to the Correct Category: Within the portal, select the category where the new article fits. 2. Create a New Article: Start creating a new article. The platform provides a text editor for you to write and format your content. 3. Write and Save as Draft: The most important feature at this stage is saving the article as a draft. This means the article is saved on the platform but is not publicly visible on your portal. Use this status to write calmly, request reviews from other team members, and ensure the information is accurate. 4. Edit and Format: Use headings, lists, and bold text to break up large blocks of text and make it easier to read. Good formatting helps the reader scan the content and find the answer more quickly. 5. Publish the Article: Once the article is finalized and approved, simply change its status from "draft" to "published". From this moment on, it will be available to everyone who accesses your Help Center. 6. Update as Needed: Products and processes change. You can edit, unpublish (revert to draft), or delete articles at any time to keep your knowledge base always up-to-date. Frequently Asked Questions How do I decide which categories to create? The best approach is to think like your customer. Analyze the most common support tickets, the most frequent questions asked of your sales team, and the natural usage journey of your product or service. Group these themes into logical and intuitive categories. For example, all billing questions could go into a "Billing and Payments" category. What is the difference between saving as a draft and publishing? An article saved as a draft is only visible to users logged into your Papo account with permission to access the Help Center. It does not appear on the public portal. A published article is visible to anyone who accesses your Help Center portal, whether a customer or an employee. Can I have one Help Center for customers and another for my team? Yes. Papo allows the creation of multiple portals. This is ideal for separating knowledge. You can have a public portal for your customers (help.yourcompany.com) and a private portal, accessible only internally, to train your team and document internal processes. Are Help Center articles used by Papo's AI? Yes. The content you publish in your Help Center can be configured as a knowledge source for Papo's artificial intelligence. This allows chatbots and AI assistants to answer questions automatically based on your official documentation, ensuring accurate and consistent responses. How do users find articles on the portal? In addition to navigating through categories, users can use the search functionality available on the Help Center portal. They can type keywords to quickly find the most relevant articles for their query, making the self-service process even more efficient. Can I add images or videos to my articles? Yes, the article editor allows you to insert media such as images and videos to make tutorials more visual and easy to follow. To manage these files, you can use Papo's File Center. Read also - Reports Overview: Where to find each metric in Papo - What are Macros and how to use them to streamline repetitive actions Start organizing your knowledge base for free → The first user on the platform is free, allowing you to start building your Help Center today.

What are Connections and how to manage them?

Connections in Papo (https://papo.global/), also known as instances, are the technical links that integrate your external communication channels — such as WhatsApp, Instagram, and Email — with the platform. They act as the "bridge" that allows messages to flow into your unified inbox. You can manage all your connections in the "Inboxes" section, located in your account's "Settings" menu. For your customer service operations to run without interruptions, it's essential that the connections to your channels are always active. Papo centralizes the management of these connections, allowing you to quickly identify and resolve issues, ensuring no customer conversation is lost. What is the difference between an Inbox and a Connection? Although the terms are used in related ways, they represent different concepts on the platform: - Connection (or Instance): This is the technical and authentication link with the source platform (e.g., Meta's API for WhatsApp and Instagram, your email server, the Telegram bot). It's the "bridge" that retrieves and sends messages. - Inbox: This is the interface within Papo where your team views and responds to conversations that arrive via a Connection. It's the workspace associated with a specific channel. In summary, every Inbox you create in Papo is powered by a Connection. The status and health of this Connection are managed through the settings of the corresponding Inbox. How to view and manage your Connections Accessing the management panel for all your connections is a simple and centralized process. Only users with administrator permissions can access this area. 1. Log in to your Papo dashboard. 2. In the sidebar menu, click the Settings icon. 3. Within the settings, select the Inboxes option. On this screen, you will find a list of all Inboxes created in your account. Each one represents an active Connection with a channel and displays a status indicator, providing a quick overview of the health of your entire communication operation. Understanding the status of each Connection Next to each Inbox, a visual indicator shows whether the connection to the source channel is working correctly. Knowing what each status means is crucial for quick action. | Status | Meaning | Recommended Action | | :--- | :--- | :--- | | Active / Connected | The Connection is working correctly. New messages are being received in real-time in your Papo Inbox. | No action is needed. Your team can continue customer service as usual. | | Inactive / Disconnected | The Connection to the source platform has been lost. New messages will not reach Papo until the issue is resolved. | You need to reconnect the channel. Click on the Inbox settings to start the reauthentication process. | | Requires Attention / Error | There is a configuration or authorization issue preventing the Connection from working. This could be a changed password, an expired token, or revoked permissions. | Check credentials and permissions on the source platform (e.g., Meta Business Suite). Follow the on-screen instructions in Papo to correct the error. | Common causes of disconnection and how to troubleshoot A Connection can be interrupted for various reasons, most of which are related to security policies or updates on the source platforms. Most common causes: - WhatsApp (Official Meta API): The password of a Meta Business account administrator was changed, or the permissions granted to Papo were manually revoked in Meta Business Manager. - Instagram and Facebook: The password of the linked Facebook account was changed. For security reasons, Meta also requires third-party app authorizations to be renewed periodically. - Email (IMAP/SMTP): Your email account password was changed, or your provider's server settings (port, SSL/TLS) were altered. - Telegram: The "Bot Token" generated by BotFather was revoked, or a new token was created, invalidating the previous one. How to reconnect a channel: When a connection fails, there's no need to create a new Inbox. Simply revalidate the existing one. 1. Navigate to Settings → Inboxes. 2. Locate the Inbox with "Inactive" or "Requires Attention" status. 3. Click the Settings icon corresponding to that inbox. 4. The platform will display a clear warning and a button to Reconnect or Reauthenticate. 5. Follow the on-screen instructions. Typically, the process involves logging back into the source platform (e.g., logging in with your Facebook account) and granting the necessary permissions for Papo to manage messages again. After following these steps, the Connection status should return to "Active" within moments. Frequently Asked Questions Where do I manage my Connections? You manage the status of your Connections in the Inboxes section, within the Settings menu. Remember that only users with administrator permissions have access to this area of the platform. What happens to messages if a Connection goes down? When a Connection is interrupted, Papo stops receiving new messages from that channel. The existing conversation history remains accessible, but no new interactions will be synchronized until the Connection is re-established. Why does my Instagram or Facebook Connection frequently disconnect? This usually happens due to Meta's security policies (the company that owns Facebook and Instagram). Meta may periodically invalidate login sessions and third-party app authorizations to protect the user's account. Changing your Facebook account password also causes an immediate disconnection. Do I need to create a new Inbox if the Connection fails? No. You do not need to create a new Inbox or lose your history. Simply follow the Reconnect or Reauthenticate process in the settings of the existing Inbox to restore the Connection. How do I know which provider my Connection uses? On the Inboxes screen, the list of connections usually displays the provider associated with each channel, such as "WhatsApp (Meta)" or "Telegram," helping to identify the origin of the connection. Can I manage Connections via the API? Yes, Papo's API allows you to list your account's instances (connections) for external monitoring. For more details on available endpoints, please consult the official API documentation. Start for free and centralize your channels → Connect your customer service channels in one place and start organizing your operations.

How to Change My Login Email and Reset My Password on Papo?

To change your login email or reset your password on Papo (https://papo.global/), you can follow two distinct processes. Changing your email is done directly within your profile settings inside the platform, while resetting your password is initiated on the login screen via the "Forgot my password" option. Keeping your login credentials updated is crucial for your account's security. Whether due to an email address change or simply forgetting your password, Papo offers simple ways for you to manage your access data. The table below summarizes the two operations so you can quickly identify which process you need to follow. | Action | Where to Perform | Main Steps | | :--- | :--- | :--- | | Change Login Email | Within the platform (logged in) | 1. Go to Settings → Profile. 2. Edit the email field. 3. Confirm the change (you may need to verify the new email). | | Reset Password | On the login screen (logged out) | 1. Click "Forgot my password". 2. Enter your login email. 3. Follow the link sent to your inbox. | How to change your login email If you still have access to your account and only wish to update the email you use to log in, the process is done within your profile settings. Remember that this email is the main point of contact for platform notifications and access recovery. Follow the steps below: 1. Log in to your Papo account: Access the platform with your current email and password. 2. Access Settings: Navigate to the Settings menu, usually located in the bottom-left corner of the screen. 3. Go to your Profile: Within the settings, find and click on the "Profile" or "My Account" option. 4. Locate and Edit the Email: On your profile page, you will find your personal details, including your name and login email. Click the option to edit or change the email field. 5. Enter the New Email: Type the new email address you wish to use to access Papo. 6. Confirm the Change: For security, you may be asked to confirm your current password or click a verification link sent to the new email address. Check your inbox and spam folder. 7. Save Changes: After confirmation, save the changes. The next time you access the platform, use the new email. How to reset your password If you have forgotten your password and cannot access your account, the way to proceed is to use the recovery function on the login screen. Follow these steps: 1. Access the Login Screen: Open your browser and go to the Papo login page (chat.papo.global/app/login). 2. Click "Forgot my password": Below the email and password fields, you will find a link with the text "Forgot my password" or similar. Click on it. 3. Enter your Email: On the new screen, type the email address associated with your Papo account and click the button to send the reset instructions. 4. Check your Inbox: Papo will send an email with a unique link to reset your password. The message may take a few minutes to arrive. Don't forget to check your spam or junk folder. 5. Create a New Password: Click the link received in the email. You will be redirected to a secure page where you can create and confirm your new password. Choose a strong password, combining letters, numbers, and symbols. 6. Log In: Return to the login screen and access your account using your email and the new password you just created. Frequently Asked Questions What happens if I no longer have access to my old email? If you can still log in to Papo with your password, you can change the email by following the steps in the "How to change your login email" section. If you cannot log in (because you forgot your password) and also no longer have access to the registered email to reset it, you will need to contact Papo support to verify your identity and request the change. I didn't receive the password reset email. What should I do? First, check your spam or junk folder. Then, confirm that you entered the email address correctly on the recovery screen. Wait a few minutes, as there might be a slight delay in sending. If, even after these checks, the email does not arrive, try the process again. If the problem persists, contact support. Can I use the same email for two different accounts on Papo? Generally, each account on the Papo platform must be associated with a unique email address. The email acts as a unique identifier for each user and their respective workspace. Attempting to create a new account with an existing email will usually result in a warning that the user is already registered. Does changing my login email affect my account integrations? No. Changing your personal login email does not affect the settings of your inboxes (such as WhatsApp, Instagram, SMTP/IMAP Email, etc.), as these are linked to the company's account, not your user profile. However, if you have any personal integrations, such as connecting with your Google Calendar, you may need to reconnect or reauthenticate them after the change. How often should I change my password? As a good digital security practice, it is recommended to change your passwords periodically, every 3 to 6 months. Additionally, you should change your password immediately if you suspect your account has been compromised or if you used the same password on another service that suffered a data breach. Start using it for free and organize your customer service → Sign up and validate the complete customer service flow with the first user for free.

How to Manage Access Permissions with Custom Roles?

In Papo (https://papo.global), custom roles allow administrators to create detailed access profiles, defining exactly what an agent can see and do on the platform. It's possible to control which conversations they access, whether they can manage contacts and reports, if they have permission to delete sent messages, and which modules (such as Kanban, Sender, Flows, and Radar) appear in their menu. An administrator creates the role in Settings → Custom Roles and then assigns it to the desired agent. Custom roles are essential for organizing teams with different responsibilities. For example, a salesperson might only need access to their own conversations and the CRM Kanban, while a support analyst might require access to all unassigned conversations and service reports. This granularity ensures that each team member has the right tools for their job, without accessing sensitive information or irrelevant functionalities. Role Tool Overview To start creating access profiles, it's important to know where to find the tool and what to expect from the creation form. Only users with the Administrator role can create and manage roles. | Item | Detail | | :--- | :--- | | Location in Menu | Settings → Custom Roles | | Who Can Access | Only users with the Administrator role | | Creation Button | Add custom role | | Required Fields | Name (minimum 2 characters), Description, and at least one permission checked | | Permission Groups | Permissions, Extra Modules, and Calls | | Available Actions | Edit and Delete an existing role | Detailing Available Permissions When creating or editing a role, you will find three main permission sections. Service and Data Permissions This group controls access to conversations and customer data. | Permission | What it grants the agent | | :--- | :--- | | Manage all conversations | Access to all conversations in the inboxes the agent belongs to. | | Manage unassigned conversations and those assigned to them | Access to conversations without a defined owner and those already assigned to the agent themselves. | | Manage conversations they participate in and those assigned to them | Access only to conversations in which the agent is a participant or owner. | | Manage contacts | Access to the CRM contact management screen. | | Manage reports | Access to the platform's reports section. | | Manage knowledge base | Permission to create and edit articles in the Help Center. | | View only my conversations | Hides the "All" and "Unassigned" tabs in the inbox, showing only the "My" tab. | | Delete already sent message | Displays the option for the agent to delete a message that has already been sent to the contact. | Extra Modules This section defines which Papo modules will appear in the left sidebar menu for the agent. If a module is not checked, it simply won't be visible. Available modules include: Kanban, Projects, Services, Sender, Email Marketing, Internal Chat, Flows / Chatbot, Sequences, Connections, CRM Reports, Call Report, Synapse, Lead Extractor, Prompt and AI, Google Calendar, Super Chat, and Radar. Calls This permission group only appears if your account has any voice call module enabled. You can define whether the agent with this role can receive calls via Wavoip, PapoCall, or WhatsApp calls (via 360Dialog). Step-by-Step to Create and Assign a Role 1. In the sidebar menu, click Settings and then Custom Roles. 2. Click the Add custom role button. 3. Fill in the role's Name (e.g., "Junior Salesperson") and a Description that helps identify its purpose (e.g., "Accesses only their own conversations and the Sales Kanban"). 4. In the Permissions section, check the conversation and data access options that the profile should have. 5. Scroll down to Extra Modules and select all modules that should be visible for this profile. 6. If applicable, configure Calls permissions. 7. Click Submit to save the new role. It will appear in the list. 8. To apply the role, go to Settings → Agents. Find the desired agent, click Edit, select the new role in the Role field, and save by clicking Edit agent. Tips for Creating Effective Roles - Start with the minimum: It's safer to create a role with the minimum necessary permissions and add more later if needed. - Use clear descriptions: When creating multiple roles, a good description helps other administrators understand who each profile is for. - Create roles by team: For sales teams that shouldn't see the general support queue, combine the permission Manage conversations they participate in and those assigned to them with the View only my conversations option. - Edit when necessary: If a process changes, you can click Edit in the role list to adjust permissions. Before deleting a role, make sure to assign a new role to all agents who were using it. Frequently Asked Questions An agent with a custom role cannot see the Kanban. Why? Most likely, the Kanban module was not checked in the Extra Modules section when creating or editing the custom role. Check the role settings. Another possibility is that the Kanban module is not enabled for your Papo account. What is the difference between "Manage all conversations" and "View only my conversations"? "Manage all conversations" is an access permission that grants viewing of all conversations in the agent's inboxes. "View only my conversations" is an interface restriction that hides the "All" and "Unassigned" tabs from the inbox, forcing the agent to focus only on the services under their responsibility. Can I grant access to the Settings area via a custom role? No. Access to the Settings area is restricted to users with the default Administrator role. Custom roles do not include permissions to manage account settings, inboxes, or other agents. How can I quickly see an agent's permissions? Go to Settings → Agents. In the list of agents, locate the "Role" column. When you hover over the name of the role assigned to an agent, an information box will appear, listing all the permissions and modules that profile has. Read also - How to create and customize your sales pipeline in CRM Kanban - How to associate inboxes with specific teams? Start for free → Centralize WhatsApp, Instagram, email, and more in one place.

Why Integrate a VOIP Telephony System like Wavoip with Papo?

Integrating a VOIP telephony system, such as Wavoip, with Papo (https://papo.global/) is essential for unifying customer communication, allowing your team to make and receive voice calls directly in the same inbox where they manage channels like WhatsApp, Instagram, and email. This centralization creates a 360° contact history, provides complete context for agents in all interactions, and enhances operations with features like AI-generated call summaries. By connecting your VOIP telephony provider, you eliminate the need for separate physical phones or softphones, transforming Papo into the central hub for all your company's communication, whether by text or voice. This not only optimizes team time but also improves customer service quality. Benefits of VOIP Integration with Papo Unifying voice and digital channels on a single platform brings strategic advantages for sales and support teams. | Benefit | Description | | :--- | :--- | | Unified History | All customer interactions (calls, chats, emails) are recorded in a single chronological profile. | | Complete Context | The agent views the entire history before or during the call, without needing to search for information in other systems. | | Operational Efficiency | Making and receiving calls on the same chat screen eliminates switching applications and using separate softphones. | | Centralized Analytics | Papo reports include call metrics (duration, volume) along with data from other service channels. | | AI Summaries | Papo's AI can generate automatic call summaries, highlighting important points and actions to be taken. | How the Integration Works in Practice With an integrated VOIP provider like Wavoip, call management becomes part of the daily workflow within Papo, seamlessly and intuitively. - Receiving Calls: When a customer calls your business phone number, a received call notification appears on the screen of agents assigned to that voice inbox. The agent can accept the call with a click and converse using their computer's microphone and audio, while viewing the entire history of previous conversations with that customer. - Making Calls: To call a customer, the agent simply accesses the contact's profile in Papo's CRM and clicks the phone icon. The call is initiated through the integrated VOIP provider, but the entire control interface (such as ending or muting the call) remains within Papo. - Automatic Logging: After the call ends, a record containing the date, time, duration, and responsible agent is automatically added to the contact's history. If your VOIP plan includes call recording, the audio can also be accessed from this history. Enhance Your Calls with Artificial Intelligence One of the biggest advantages of centralizing voice calls in Papo is the ability to apply Artificial Intelligence to conversations. With Papo's AI module, it's possible to generate automatic summaries for each call. At the end of a call, the AI processes the audio (if recording is available through the VOIP provider), transcribes the conversation, and creates a concise summary, highlighting key discussion points, decisions made, and next actions. This saves valuable agent time, as they no longer need to write manual notes, and ensures no important information is lost. How to Integrate Your VOIP System (Example with Wavoip) The integration process is designed to be simple and fast, requiring only your VOIP provider's credentials. Using Wavoip as an example, the steps are as follows: 1. Obtain the API Token: Access your administrator panel in Wavoip and copy the API token. 2. Create the Inbox in Papo: In your Papo account, go to Settings → Inboxes and click Add inbox. 3. Select the Channel: Choose the Voice channel and select Wavoip as the provider. 4. Configure and Save: Give the inbox a name (e.g., "Sales - Calls"), paste the Wavoip token, and save the configuration. 5. Assign Agents: Add the agents or teams who will have permission to use this channel to make and receive calls. Once completed, the voice channel will be active and ready for use. Frequently Asked Questions (FAQ) Do I need to have a Wavoip account already to integrate? Yes. Papo's integration connects to your existing VOIP telephony account. You need to have an active plan with a provider like Wavoip to obtain the necessary credentials (such as the API token) and for the call service to function. Are all calls recorded in Papo? Papo records the metadata of all calls, such as date, time, duration, and the agent involved. Call audio recording depends on the settings and plan you have with your VOIP provider (e.g., Wavoip). If recording is enabled with the provider, it will be accessible in the contact's history in Papo. Besides Wavoip, what other VOIP providers can I integrate? Papo integrates with leading VOIP providers, such as Wavoip and Twilio. To check the complete list of available integrations or discuss the possibility of connecting another provider, consult the channels section on the platform or contact our support team. How does AI summarize voice calls? After a call is completed, if audio recording is available through your VOIP provider, Papo can send this audio to its Artificial Intelligence engine. The AI transcribes the conversation and then generates a concise text summary highlighting key points, which is automatically attached to the call record in the customer's history. Does VOIP integration work with other Papo automations? Yes. Channel unification allows you to create more powerful automations. For example, after a recorded call, an agent can use a Macro to send a follow-up message via WhatsApp with one click, or an incoming call from a new number can trigger an Automation Flow to qualify the lead. Is the cost of calls charged by Papo? No. Papo provides the platform to unify and manage calls. Costs related to call rates (per minute, per call, etc.) are billed directly by your VOIP telephony provider, according to the plan you have contracted with them. Read Also - How does AI call summarization work? - Which service channels can I connect to Papo's inbox? Start for free and centralize your customer service → Unify your voice calls, WhatsApp, Instagram, and email in a single platform.

How to send new conversation notifications to Slack using Webhooks

To receive a notification in Slack every time a customer starts a conversation in a specific inbox in Papo (https://papo.global/), you must set up a Flow that triggers a Webhook to the desired channel. This keeps your support or sales team alerted in real time, without having to constantly monitor the platform. The integration uses Slack incoming Webhooks and Papo Flows to turn a new conversation into an instant alert. Without complex code, you can choose the inbox, customize the message content, and ensure no one misses an important lead or ticket. | Step | Action | Tool | | :--- | :--- | :--- | | 1. Prepare Slack | Create an App and enable Incoming Webhooks to get the sending URL | api.slack.com | | 2. Create the Flow in Papo | Set up a new flow with a “New conversation” trigger and a “Webhook” action | Flows module (Papo) | | 3. Test the notification | Start a conversation in the chosen inbox and check that the message arrives in the Slack channel | Slack + Papo | How it works — step by step 1. Get the Webhook URL in Slack First, you need an incoming Webhook in Slack. Go to the Slack API (api.slack.com), create an App (or use an existing one), enable Incoming Webhooks, and generate a unique URL for the channel where alerts will be posted. Note this URL — it will be used in the Papo Flow. 2. Create a new Flow in Papo In the Papo dashboard, go to the Flows module and click to create a new flow. Give it a name that identifies the notification, such as “New conversation alert in Slack”. 3. Configure the trigger Add a Trigger node and define that the flow should start when a New conversation arrives. Choose the specific inbox (for example, the WhatsApp number, Instagram, or another connected channel) that should generate the alert. It is possible to filter by message type or channel, depending on your support structure. 4. Add the Webhook action After the trigger, insert an Action node and select the Send Webhook option (or similar). In the configuration field: - URL: paste the Slack Webhook URL obtained in step 1. - Method: keep it as POST. - Payload: define the content that will be sent. You can use variables available in the conversation context, such as {{contact.name}}, {{message.text}} or {{inbox.name}}, to build a personalized message. For example: { "text": "New conversation from {{contact.name}} in inbox {{inbox.name}}: {{message.text}}" } - Adjust headers if necessary (the default usually works). 5. Activate the Flow and test Save and activate the flow. To test, send a message to the configured inbox — for example, message your own WhatsApp number connected to Papo. Within seconds, the notification should appear in the selected Slack channel. If it does not arrive, check whether the flow is active and whether the Webhook URL is correct; you can also review the execution log inside the Flows module itself. Who this integration is useful for - Support teams that use Slack as their communication hub and need immediate alerts about new tickets. - Sales teams that monitor incoming leads on specific channels, such as a campaign WhatsApp inbox. - Operations with multiple channels that want to consolidate notifications in one place, without switching between tabs. Frequently asked questions Do I need a Webhook configured in Slack before using the Flow? Yes. You need to create an App in Slack, enable Incoming Webhooks, and copy the generated URL. This procedure is done outside Papo, in Slack's developer interface. Can I send the exact content of the customer's message in the alert? Absolutely. Inside the payload of the Webhook action, you can include dynamic variables such as the conversation text, contact name, and channel, building a rich and contextual notification. What happens if the request to Slack fails? The Flow will log the error. You can add failure handling actions, such as sending an email or creating an internal task, to ensure the team does not miss the critical alert. Is it possible to send notifications to different Slack channels depending on the inbox? Yes. Simply create a separate Flow for each inbox and point to the Webhook URL of the desired Slack channel. This way, support conversations go to one channel, and sales leads to another. How do I test without bothering the team? After activating the flow, use a test contact — such as your own personal number — and send a message to the configured inbox. Confirm that the notification appears only in the designated channel. You can delete the test flow after validating. Is there an additional cost to use Webhooks in Papo? Flows and Webhook sending features are included in Papo plans. Detailed information about limits and subscriptions is available on the official website. Read also - How to create an automation that sends a message after a specific time? Start for free and integrate Slack → Create your free Papo account and connect your channels to receive Slack alerts at no initial cost.

How to integrate Papo with n8n to automate processes

To integrate Papo (https://papo.global/) with n8n and automate processes, you can use the platform's API keys to send contact data, manage conversations, or trigger actions, and also configure webhooks in Automation Flows so that Papo notifies n8n whenever an event occurs, such as a new message or a qualified lead. Papo offers two main ways to communicate with n8n, one of the most popular automation platforms. The first is the API, which allows n8n to make active calls to Papo (for example, to create a contact or send a message). The second is webhooks, which work in the opposite direction: Papo automatically sends information to n8n when something happens within a service flow. | Integration Method | Direction | Main Use | How to Configure | | :--- | :--- | :--- | :--- | | Papo API | n8n → Papo | Send commands to Papo (create contact, send message, fetch data). | Generate a secret key in the Papo dashboard and use n8n's HTTP Request node with Bearer authentication. | | Papo Webhook | Papo → n8n | Receive automatic notifications from Papo when an event occurs (new conversation, qualified lead). | Create a Webhook node in n8n to generate a URL and configure the "Send Webhook" action in a Papo Flow. | How the API integration works Papo's API is the gateway for n8n to execute actions in your account programmatically. With it, you can automate tasks such as syncing contacts with an external CRM, triggering WhatsApp messages from a trigger, or extracting lead data. 1. Generate your API keys in Papo Go to your Papo dashboard and navigate to Settings. In the Developers or API section, you will find your Public Key (fixed) and can generate a Secret Key. Give it a descriptive name (e.g., "n8n Integration") and copy the secret key immediately — it will be displayed only once. 2. Configure the HTTP Request node in n8n Inside a workflow in n8n, add an HTTP Request node. In the URL field, use the desired Papo API endpoint. The base URL is: https://app.papo.global/api/v1 To authenticate, add an Authorization header with the value Bearer sk_live_YOUR_SECRET_KEY. A good initial test is to call the /me endpoint, which returns your account data: GET https://app.papo.global/api/v1/me Authorization: Bearer sk_live_... 3. Build your automation flow With authentication working, you can create complete workflows. For example: - New form lead → create contact in Papo: a Webhook node in n8n receives the form data, and an HTTP Request node calls the Papo API to create the contact. - Fetch extracted contacts and send to a spreadsheet: n8n periodically queries the Extractor contact list and inserts them into Google Sheets. Papo's API allows you to fetch, create, and update contacts, send WhatsApp messages, list Extractor runs, and much more. Full documentation with all endpoints is available at papo.global/pt/docs. How the Webhooks integration works Webhooks are ideal for reacting to events that happen within Papo in real time. You configure a Flow to trigger an automatic notification to n8n whenever a contact reaches a specific step. 1. Create a Webhook trigger in n8n In the n8n editor, add a Webhook node as the trigger for your workflow. Choose the POST method and copy the generated production URL. This URL will be the destination for data sent by Papo. 2. Configure the "Send Webhook" action in the Papo Flow Inside the Papo Flow editor, add the "Send Webhook" action node at the point in the journey where you want the notification to occur (for example, right after a lead answers a qualification question). Fill in the fields: - Webhook URL: paste the URL copied from n8n. - HTTP Method: select POST. - Body (Payload): build a JSON with the contact variables you want to send. Example: { "name": "{{contact.name}}", "email": "{{contact.email}}", "phone": "{{contact.phone}}", "stage": "Qualified lead", "source": "Welcome Flow" } 3. Test and activate Before publishing, test with a service URL like Webhook.site to verify that the data arrives correctly. Then replace it with the n8n URL and activate the Flow. From that moment on, every time a contact passes through this node, n8n will receive the data and can execute actions such as registering the lead in a CRM, sending an email, or updating a spreadsheet. Who this integration is for The connection between Papo and n8n is useful for companies that already use Papo as a WhatsApp customer service and sales hub and need to connect these processes to other systems without relying on internal development. Marketing agencies, sales teams, and support operations can, for example, automatically sync contacts between Papo and an ERP, launch segmented campaigns, or create custom dashboards. Frequently Asked Questions (FAQ) Do I need to know how to code to integrate Papo with n8n? No. n8n is a visual automation tool, and configuring the API or webhook is done by filling in fields and assembling small JSON blocks. Basic knowledge of REST APIs helps, but it is not required. What Papo actions can I automate with the API? You can fetch, create, and update contacts, send WhatsApp messages, list contacts extracted by the Extractor, query run data, and much more. The complete list is in the official documentation. Does the Papo webhook send data in real time? Yes. As soon as the contact reaches the "Send Webhook" node in an active Flow, Papo immediately sends the request to the configured URL. Can I use the API to create a contact in the CRM from a form on my website? Yes. Simply configure a Webhook node in n8n to capture the form data and then an HTTP Request node to call the Papo API and create the contact with the received information. Where can I find the complete Papo API documentation? The technical documentation with all endpoints, parameters, and examples is available at papo.global/pt/docs. Are the API and webhooks available on the free plan? Yes, both the API and webhooks are part of the platform and can be used by any Papo account. You can start for free with the first user and test all integrations. Read also - How to send notifications for new conversations to Slack using Webhooks Start free with Papo Global → The first user is free, and you can already test the API and webhooks to automate your processes at no cost.

How to receive notifications of new conversations by email

To receive an email notification whenever a customer starts a conversation in a specific inbox in Papo (https://papo.global/), you must configure a Flow with the “New conversation” trigger and a Webhook action pointing to an email or automation service that turns the trigger into an alert in your inbox. This keeps your team informed in real time, without having to constantly monitor the platform. Papo does not send the email directly in this scenario. What it does is trigger a Webhook with the new conversation data. An external email service — such as an automation tool, transactional email, or your own endpoint — receives that Webhook and generates the alert in the desired inbox. | Step | Action | Tool | | :--- | :--- | :--- | | 1. Prepare the destination | Create an automation or endpoint that receives the Webhook and sends the email | Email/automation service | | 2. Create the Flow | In the Flows module, create a flow with the “New conversation” trigger and “Send Webhook” action | Flows module (Papo) | | 3. Configure sending | Provide the endpoint URL and build the payload with conversation variables | Flows + endpoint | | 4. Activate and test | Start a conversation in the chosen inbox and check that the email arrives | Papo + email | How to configure email notification 1. Prepare the Webhook destination First, you need an endpoint capable of receiving Papo’s Webhook and turning the call into an email. This can be done in an email automation tool, a transactional service, or your team’s own Webhook. The important thing is to have a destination URL that accepts POST requests and triggers the email to the desired recipients. 2. Create the Flow in Papo In the Papo dashboard, go to the Flows module and create a new flow. Give it a name that identifies its purpose, such as “New conversation email alert”. 3. Set the trigger as “New conversation” Add a trigger node and choose the New conversation option. Select the inbox that should generate the alerts — for example, the WhatsApp number, email, or another channel connected to Papo. You can keep the alert restricted to a specific inbox, avoiding noise in other operations. 4. Add the “Send Webhook” action After the trigger, insert an action node and select Send Webhook (or the equivalent option available in the Flows module). Fill in the main fields: - URL: paste the URL of the endpoint prepared in step 1. - Method: use POST, which is the appropriate method for sending data in the request body. - Payload: build the content in JSON with the dynamic conversation variables. Example: { "contact_name": "{{contact.name}}", "message_text": "{{message.text}}", "inbox_name": "{{inbox.name}}" } The variables will be replaced by the real conversation data at the moment the trigger fires. 5. Activate and test the flow Save and activate the flow. Then send a test message to the configured inbox. If the endpoint and payload are correct, the email will arrive shortly. If it does not arrive, review the flow, the URL, and the execution log of the Flows module; also confirm that the email service is receiving the request and sending the alert. Who this configuration is useful for - Support teams that work outside Papo and want to be notified by email for every new conversation. - Operations with multiple inboxes that want to centralize alerts in a corporate email inbox. - Managers who need to track the volume of new conversations without opening the dashboard constantly. - Companies that already use email as an official internal trigger channel. FAQ Do I need an external email service to receive notifications? Yes. The Papo flow sends a Webhook; the endpoint you configure turns that Webhook into an email. Papo does not send the email directly in this scenario, so you need an automation service, a transactional email, or your own endpoint. Can I choose which inboxes generate alerts? Yes. In the New conversation trigger, you define the specific inbox that will be monitored. To notify different inboxes to different recipients, create a separate flow for each inbox and point it to the corresponding email endpoint. What information can I include in the email? You can include variables available in the conversation context, such as {{contact.name}}, {{message.text}}, and {{inbox.name}}. In the email service, these fields can be mapped to the subject and body of the message. What happens if the Webhook request fails? The Flow logs the error in the execution log. You can add handling actions, such as a retry or an alternative alert, to reduce the risk of missing an important notice. How do I test without sending emails to the entire team? Use a test contact — for example, your own WhatsApp number or a secondary email address — and send a message to the configured inbox. Check that the email arrives only at the test destination before putting the flow into production. Is there an additional cost to use Flows and Webhooks in Papo? The Flows and Webhook sending features are part of Papo plans. Details about limits and subscriptions are available on the official website. See also - How to create a flow that sends a daily summary of conversations by email Start for free and set up your new conversation alerts → Create your free Papo account and use Flows with Webhooks so you never miss a new conversation in your inbox.

How to reconnect Google Calendar when schedule synchronization fails

If synchronization between Papo (https://papo.global/) and your Google Calendar has failed, the fastest solution is to revoke the old authorization and reconnect the Google account, confirming calendar access permissions. After reconnecting, the platform reads your busy times in real time again and creates events automatically, eliminating conflicts and manual rescheduling. When the AI stops suggesting free times, rescheduled appointments do not appear on the calendar, or the integration status shows “disconnected,” reconnecting is the first step. This page gathers the essential checks and the step-by-step to restore synchronization safely. | Situation | Likely cause | Recommended action | | :--- | :--- | :--- | | The AI does not offer free times | Lost connection or revoked permissions | Reconnect Google Calendar | | WhatsApp events do not appear on the calendar | Missing permission to create events | Reauthorize permissions during reconnection | | Calendar does not sync | Wrong Google account or expired authorization | Connect with the correct account that contains the appointments | These fixes do not require any advanced configuration. In the vast majority of cases, reconnecting resolves the problem immediately. Before reconnecting: check the connection status Inside the Papo platform, the integrations area shows the Google Calendar status. If it displays “disconnected,” Papo cannot read busy times or create new events on your calendar. Also confirm which Google account is authorized. It can be a personal account (@gmail.com) or a professional Google Workspace account. The connected account must be exactly the one you use to check your appointments. If the authorization is linked to an old or secondary account, events may be going to the wrong calendar. Step-by-step to revoke and reconnect access 1. Go to Papo integrations Locate the Google Calendar option. On some accounts, this integration is in the Appointments module or in the general Integrations section of settings. 2. Start reconnection Click the Google Calendar integration. If there is a previous connection, the flow will let you revoke it and start a new link, clearing the previous state. 3. Sign in to the correct Google account Google will ask for email and password. Use the account that contains your appointments and where you want Papo events to be created. 4. Authorize the necessary permissions Google displays an authorization screen. Grant the permissions so Papo can read your busy times and create events on your behalf. Without these two permissions, synchronization will not work. 5. Confirm the final status After authorizing, you return to Papo. The integration should appear as “Connected,” indicating that synchronization is active again. How to confirm it is working again Once the connection is restored, Papo checks your Google Calendar in real time again. This means that: - existing personal or professional appointments are now considered busy times; - the AI does not offer already booked times during a WhatsApp conversation; - when an appointment is confirmed, an event is created automatically in Google Calendar with the customer's data. To test, you can simulate an appointment request or check whether your calendar appointments are reflected in Papo's appointments view. Who this fix matters for Google Calendar integration is essential for businesses that depend on scheduled times. When synchronization fails, clinics, medical offices, beauty salons, law firms, accounting offices, and service providers risk offering duplicate times or losing appointments. Keeping the connection active avoids the manual work of copying information between chat and calendar, reduces human errors, and ensures that no appointment is overlapped. Frequently asked questions What permissions does Papo need in Google Calendar? Papo needs permission to read your busy times and to create events on the calendar. These permissions are requested by Google during connection and must be confirmed for synchronization to work. How do I know if Google Calendar is connected? Check the Google Calendar connection status in your Papo account. When connected, the integration is active and the system again considers your calendar for availability and event creation. Can I use a Google Workspace account? Yes. The integration accepts both personal accounts (@gmail.com) and professional Google Workspace accounts. The important thing is to use the correct account at the time of authorization. Is synchronization in real time? Yes. After reconnection, Papo checks your Google Calendar in real time to know which times are busy and avoid conflicts in rescheduling. What should I do if the problem persists after reconnecting? Confirm that the authorized Google account is exactly the one that contains your appointments. If the account is correct and the status shows “Connected” but the times still do not reflect, contact Papo support for a more detailed analysis. Read also - How to troubleshoot Google Calendar synchronization issues Start for free and sync your Google Calendar now → The first user is free and no credit card is required — connect your calendar and let the AI reschedule for you.

How to generate a Papo public key and secret API key

To generate Papo API keys (https://papo.global/), go to the dashboard and navigate to Settings > Developers (or API). There you'll find your fixed public key and can create named secret keys, which are shown only once and must be stored in a secure location, such as a password manager or server environment variables. The Papo API uses a key pair to identify and authenticate your account in integrations with CRMs, ERPs, automation platforms (n8n, Zapier), and your own systems. Understanding the difference between them and knowing how to generate and protect them is the first step to building reliable automations. | Key Type | Format | Purpose | Exposure Level | | :--- | :--- | :--- | :--- | | Public Key | pk_live_... | Uniquely identifies your Papo account. | Can be exposed in the frontend or in public scripts. | | Secret Key | sk_live_... | Authenticates requests and authorizes actions on your account. | Confidential – must never be shared or stored in code. | How to generate the API keys 1. Log in to the Papo dashboard and go to Settings. 2. In the side menu, find the Developers or API section. 3. The page will display your Public Key (pk_live_...). It is fixed and can be copied at any time. 4. To obtain a Secret Key, click the button to create a new key. 5. Give it a descriptive name (e.g., “CRM Integration”, “n8n Automation”) to make future management easier. 6. The secret key (sk_live_...) will be displayed only once. Copy it immediately and store it in a secure location. ⚠️ For security, Papo stores only the hash of the secret key. If you lose the original value, it cannot be recovered. In that case, revoke the compromised key and generate a new one. How to store the keys securely - Never put the secret key directly in source code, Git repositories, or messages. - Use environment variables on your server (e.g., PAPO_SECRET_KEY) and reference them in code. - Store the key in a password manager (such as 1Password, Bitwarden, or your cloud provider's vault) for future reference. - If the key leaks or is suspected of being compromised, go to the same developers page, find the key in the list, and revoke it immediately. Then create a new one and update your integrations. What are these keys for? The keys are used in all calls to the Papo API that require authentication. The secret key is sent in the Authorization header as a Bearer token. The public key can be sent in the X-Papo-Public-Key header as additional verification, but primary authentication always depends on the secret key. With the keys in hand, you can, for example: - Send WhatsApp messages via API. - Query contacts extracted by the Extractor. - Trigger Papo's artificial intelligence from your system. - Sync data with your CRM or ERP. Frequently Asked Questions Where can I find my account's public key? The public key (pk_live_...) is visible on the Settings > Developers (or API) page. It is fixed and can be copied whenever needed. Can I have more than one secret key? Yes. You can generate multiple secret keys, each with a different name (e.g., “Production”, “Test”, “n8n”). This helps isolate access and revoke a specific key without affecting the others. I lost my secret key. What should I do? The secret key cannot be recovered. Go to the developers page, revoke the lost key, and create a new one. Update your integrations with the new value. Do I need the public key to authenticate? Not necessarily. Authentication is done by the secret key. The public key is optional and serves as an additional identifier, but it does not replace the secret key. How do I revoke a secret key? In the key list on the developers page, find the key you want to disable and click the revoke option. From that point on, any request using that key will be refused. Can I use the keys in tools like n8n or Zapier? Yes. Papo API keys are compatible with any tool that supports Bearer token authentication. Simply enter the secret key in the tool's authorization field. Read also - How to integrate Papo with n8n to automate processes Start for free → Create your free Papo account and get immediate access to the API keys to integrate your systems.

How to send new contact data to Google Sheets via webhook

To automatically send the name, phone number, and email of new contacts to Google Sheets, use the Papo (https://papo.global/) Flows module to create an automation with a new contact trigger and a webhook action. The action sends the contact data to a URL prepared in Google Sheets through an automation platform such as Zapier or Make, or through a Google Apps Script. This integration eliminates manual exports and keeps a lead spreadsheet always up to date. Every time a contact enters the Papo CRM, the Flow fires the webhook and records the information in a new row in Google Sheets. Integration overview | Step | Where it happens | What it does | | :--- | :--- | :--- | | 1. Prepare the destination | Google Sheets + external tool | Create the spreadsheet and generate a webhook URL with Zapier, Make, or Google Apps Script. | | 2. Create the trigger | Papo (Flows) | Define the "Contact Created" event to start the automation when a new lead enters the CRM. | | 3. Configure the webhook | Papo (Flows) | Add the webhook action with the destination URL and the JSON body containing name, phone number, and email. | | 4. Receive and record | Google Sheets | The URL receives the payload and inserts a new row in the spreadsheet with the contact data. | | 5. Use the data | Google Sheets / other tools | Track leads, build reports, or connect the spreadsheet to dashboards. | How to prepare Google Sheets to receive the data Papo does not generate the Google Sheets URL. You need to create an endpoint that receives the JSON sent by the webhook and writes the data to the spreadsheet. There are two common ways to do this. Option A: no-code automation platform Tools such as Zapier or Make let you create a "Catch Webhook," which generates a unique URL. Then you add an "Add Row" action in Google Sheets, mapping the received fields to the spreadsheet columns. This is the recommended option for those who don't want to code. The platform handles authentication with Google and writing to the spreadsheet. Option B: Google Apps Script In Google Sheets, open Extensions > Apps Script, paste code with the doPost(e) function that parses the JSON and inserts the data. Deploy it as a "Web App" with access set to "Anyone" and copy the generated URL. This option offers more control, but it requires basic knowledge of JavaScript and of Google's deployment interface. Setting up the Flow in Papo With the webhook URL in hand, go to the Flows module in Papo and create a new automation. 1. Define the trigger: choose the "Contact Created" event. This will make the Flow fire as soon as a new contact is added to the CRM. 2. Add the webhook action: in the Flow editor, include a Webhook step. 3. Fill in the URL: paste the address generated in Zapier, Make, or Apps Script. 4. Keep the method as POST. 5. Build the message body in JSON with the fields you want to export. Example: { "name": "{{contact.name}}", "phone": "{{contact.phone}}", "email": "{{contact.email}}" } 6. Save and activate the Flow. From that moment on, every new contact that enters Papo will be automatically recorded in the Google Sheets spreadsheet, with no manual action. Who this automation is for - Sales teams that need a centralized, always up-to-date lead base. - Marketing analysts who want to track the volume of contacts generated by channel or campaign. - Sales operations that already use Google Sheets as a data hub and want to eliminate manual exports. - SDR teams that need to trigger follow-up routines from newly registered contacts. Frequently asked questions Do I need to know how to code to set up the webhook? Not necessarily. With Zapier or Make, the integration is done without code. Only the Google Apps Script option requires basic knowledge of JavaScript. Is the data sent in real time? Yes. As soon as the "Contact Created" trigger fires in Papo, the webhook sends the data immediately to the configured URL. What information can I send to Google Sheets? You can send the name, phone number, email, and other data available in the Flow variables. The exact variables can be found in the Flows module documentation. Can I test before activating the Flow? Yes. You can create a test contact in Papo and check whether the row appears in the spreadsheet. You can also send a test from the tool that generated the URL. Does Papo provide the webhook URL? No. The URL must be created in Zapier, Make, or Google Apps Script. Papo only sends the data to the configured address. Read also - How to export sales funnel data to Google Sheets and create custom dashboards - How to personalize automated messages with the contact's name and data Start for free → You can create your account and validate the automatic sending of contacts to Google Sheets with the first user for R$ 0.

How to Embed the Help Center on Your Website Using a Code Snippet

To embed the Papo Help Center (https://papo.global/) on your website, go to the Help Center module in the dashboard, generate the code snippet, and paste it into the HTML of the pages where you want to display the knowledge base. The Papo Help Center is a public article base that you can make available directly on your website. With a simple snippet, your customers can browse tutorials, FAQs, and guides without leaving your page, reducing repetitive tickets and improving the self-service experience. Embedding overview | Step | Action | Description | |------|--------|-------------| | 1 | Access the Help Center module | In the Papo dashboard, go to the Help Center module. | | 2 | Generate the embed code | Find the embed option and copy the HTML snippet. | | 3 | Paste into your website's HTML | Insert the code where desired, before the closing </body>. | | 4 | Publish and test | Save the page and check that the Help Center loads correctly. | How embedding works Papo lets you turn the Help Center into an embeddable widget. The generated snippet loads a responsive version of your knowledge base, which automatically adapts to your website's layout. Visitors can search articles, browse categories, and read the full content without opening another tab. Articles are updated directly in the Papo dashboard. Any change — new text, image, or category — is reflected instantly in the embedded version, with no need to edit the code again. Step-by-step guide to embedding 1. Access the Help Center module In the Papo dashboard, find the Help Center module. This is where you manage your public articles. 2. Generate the embed snippet In the Help Center settings, look for the embed option. The platform will display an HTML code snippet ready to copy. 3. Copy the code Select the entire snippet and copy it to your clipboard. The code includes the references needed to load the Help Center on your domain. 4. Paste it into your website's HTML Insert the snippet into the source code of the pages where you want to display the Help Center. The most common location is before the </body> tag, but you can place it in any section that makes sense for your layout (e.g., support page, FAQ, or help center). 5. Publish and test Save your changes and visit the published page. The Help Center should appear as an integrated block. Run a test search to confirm that the articles are accessible. Who this feature is useful for - Companies that want to reduce ticket volume – customers find answers on their own before opening a ticket. - E-commerce and SaaS websites – offer contextual support during browsing. - Operations with lean teams – the knowledge base works 24/7, even when no agents are available. - Any business already using Papo – embedding is native and requires no external integrations. Frequently asked questions Does the snippet affect website performance? No. The code is lightweight and loads asynchronously, without impacting your page load times. Can I customize colors and fonts? Yes. Papo offers basic customization options so the Help Center matches your website's visual identity. The settings are available in the Help Center module itself. Does the embedded Help Center work on mobile devices? Yes. The widget is responsive and automatically adapts to smartphone and tablet screens. Do I need a specific plan to use embedding? The Help Center is available on all Papo plans. The embedding feature is part of the module, at no extra cost. How do I update the articles displayed? Simply edit or publish new articles in the Papo dashboard. The embedded version reflects changes in real time, without you needing to change the snippet. What should I do if the snippet doesn't load? Check that the code was pasted correctly and that no script blockers (such as privacy extensions) are preventing it from loading. Also make sure your website domain is authorized in the Help Center settings. Read also - How to embed the Papo website chat in WordPress Start for free and embed the Help Center in minutes → With Papo, you provide support directly on your website and keep all customer service centralized in the same dashboard.

How to set up two-factor authentication (2FA) on your Papo account

Papo Global (https://papo.global/) lets you add an extra layer of security to your account with two-factor authentication (2FA), using authenticator apps to confirm login. This article explains what 2FA is, why to enable it, and how to prepare; the exact setup details are in the account security area and on the official website. Two-factor authentication reduces the risk of unauthorized access, even if someone discovers your password. Instead of relying only on something you know (your password), 2FA also requires something you have (a temporary code generated on your phone). Summary of what you need | Step | What you need | Goal | |---|---|---| | 1. Access the account security area | Active login to Papo Global | Find the authentication options | | 2. Install an authenticator app | Google Authenticator, Authy, or similar | Generate temporary verification codes | | 3. Save recovery codes | Provided codes or QR code | Recover access if you lose your phone | | 4. Confirm activation | Code generated in the app | Validate 2FA and protect login | What two-factor authentication is Two-factor authentication is a security method that requires two forms of verification before granting access. In practice, you enter your password and then a one-time code generated by an authenticator app. This code changes every few seconds and only appears on the device linked to your account. Why enable 2FA on Papo Papo centralizes customer conversations, CRM data, reports, and integrations. A compromised account can expose sensitive information and disrupt service. With 2FA, even if your password leaks or is guessed, an attacker cannot sign in without the code from your phone. This precaution is especially important for: - Administrators who manage agents, channels, and settings. - Agents who access conversations and customer data. - Teams that use Papo on multiple devices or outside the office. How 2FA works with an authenticator app After you enable 2FA, the login flow has an additional step: 1. You sign in to Papo with your email and password. 2. The platform requests a verification code. 3. You open the authenticator app on your phone, copy the displayed code, and enter it on the screen. 4. If the code is correct, access is granted. Apps such as Google Authenticator, Authy, and Microsoft Authenticator work without an internet connection after the initial setup. They generate codes based on a shared secret between the app and the platform. What to do before enabling 2FA Before enabling it, prepare these items so you do not get locked out: - Install an authenticator app on the phone you use every day. - Save the recovery codes provided during setup. They let you sign in to your account if your phone is lost or replaced. - Make sure your recovery email is up to date. A valid email helps you reset your password and recover access. - Avoid enabling 2FA on a shared device. The device that generates the codes should be personal and protected by a password or biometrics. Where to enable 2FA on Papo The Settings area of your Papo account contains the options related to security and access. Because the interface may be updated frequently, we recommend checking the official page or the Papo Global help center for the updated step-by-step instructions and the exact screen names. We do not reproduce clicks or menu paths here that are not documented in the provided reference materials. Frequently asked questions What is two-factor authentication? It is an extra layer of security that requires, in addition to your password, a temporary code generated by an authenticator app. This way, login is only completed by someone who has access to the linked device. Do I need to use an authenticator app? Yes, the format described in this guide uses authenticator apps, such as Google Authenticator or Authy. Other methods may exist depending on your account configuration; check the Papo security area to confirm the available options. Is 2FA mandatory on Papo Global? Whether it is mandatory may vary depending on the account type or company policies. Check your account security settings or ask an administrator to find out whether 2FA is required in your case. What happens if I lose my phone? If you lose your phone, use the recovery codes saved during activation to access your account and set up a new device. Without the codes, support may request other identity verifications. Where can I find the 2FA settings in my Papo account? The security options are inside the account settings area. To see the exact path and current screens, visit the official Papo Global website or the help center. Can I use SMS instead of an authenticator app? The availability of alternative methods, such as SMS, depends on the options offered in your account. Check the Papo security area to see which methods are enabled. Read also: How to generate a public key and a secret key for the Papo API · How to set up Papo in 5 steps to start serving customers on WhatsApp Start free on Papo Global → First user free, no credit card required. Learn more at papo.global.

How to use Papo on multiple devices at the same time without conflict

Papo (https://papo.global/) is a 100% web-based platform, which means you can access your account from any device with a browser and internet connection, simultaneously, without conflicts. There is no limit on active sessions: you can be logged in on your office computer and your phone at the same time, and all conversations, contacts, and settings are synchronized in real time. | Situation | Recommendation | | :--- | :--- | | Accessing from multiple devices | Log in with your email and password in each browser. Papo does not restrict the number of simultaneous sessions. | | Keeping synchronization | Any action (replying to a message, moving a card in Kanban) appears instantly on all logged-in devices, because the platform is cloud-based. | | Avoiding disconnections | Use a stable internet connection and keep your browser up to date. If there is a drop, just reload the page. | | Security on shared devices | Never save your password on public computers. When you finish, log out. Enable two-factor authentication (2FA) to protect your account. | | What to do if you forget to log out of a device | If you have lost access to a device where you were logged in, change your password immediately. This will require a new login on all devices. | How simultaneous access works Because it is a web application, Papo does not require installing programs. Just open your browser (Chrome, Firefox, Safari, Edge) and go to chat.papo.global. On mobile devices, you can use your phone's browser or add the shortcut to your home screen for an app-like experience. Since all processing happens on Papo's servers, each device maintains an independent session, but always connected to the same real-time database. This eliminates version conflicts: if you start a conversation on desktop and then open your phone, you will see the same conversation exactly as you left it. Who it is useful for - Teams that alternate between office and field – salespeople who use desktop in the office and mobile during visits. - Managers who monitor operations on the go – track queues, answer internal questions, and approve actions on their phone while the team works on computers. - Agents who need flexibility – can start a conversation on a computer and continue on a tablet or smartphone without losing context. Frequently asked questions Can I use Papo on my computer and phone at the same time? Yes. Just go to chat.papo.global in the browser on both devices. The sessions are independent and do not interfere with each other. Do I need to install an app to use it on my phone? No. Papo is a web platform, accessible directly through your smartphone's browser (Chrome, Safari, etc.). You can even add the shortcut to your home screen to access it like an app. If I reply to a message on my phone, does it appear on my computer? Yes. All communication is synchronized in real time. The conversation you start on one device will be instantly available on the other. Is there a limit on devices connected at the same time? There is no limit defined by the platform. You can keep sessions open on as many devices as you want, as long as you use your account credentials. How do I end a session on another device? Papo does not have an active session management panel. To end access on a device you do not control, change your account password. This will require a new login on all devices. As a preventive measure, always log out when using shared computers. Can simultaneous use cause conflicts or data loss? No. Because it is a cloud application, Papo manages updates centrally. Two people using the same account on different devices can, for example, edit the same record, but the last change will prevail, without corrupting the data. For teamwork, it is best for each agent to have their own user. Read also - How to set up two-factor authentication (2FA) on your Papo account Start using Papo on all your devices now → The first user is free forever, no credit card required.

How to test a Papo webhook connection before activating automation

To test a Papo (https://papo.global/) webhook connection before activating automation, you can use an external tool such as Webhook.site to validate the destination URL, check the JSON payload format, and fix sending errors without affecting real contacts. This process works both for native account webhooks and for the “Send Webhook” action inside Automation Flows. Early validation prevents a broken integration from losing data or interrupting customer journeys. With a temporary test URL, you can inspect exactly what Papo is sending — headers, body, and response codes — and make adjustments before pointing to the final system. Test process summary | Step | Action | Tool / location | | :--- | :--- | :--- | | 1. Get a test URL | Go to webhook.site and copy the generated URL. | Webhook.site | | 2. Configure the webhook in Papo with the test URL | Enter the URL in the webhook destination field (in the Integrations section or in the Flow action). | Papo dashboard | | 3. Trigger the webhook | For account webhooks, send a WhatsApp message to the connected inbox. For webhooks in Flows, enroll a test contact in the flow. | Inbox or Flow | | 4. Analyze the received payload | In the Webhook.site dashboard, view the request that arrived: method, headers, and the JSON body. | Webhook.site | | 5. Fix and replace with the production URL | If the payload is correct, replace the test URL with your system’s real URL and activate the automation. | Papo dashboard | How to test account webhooks (Integrations) Papo native webhooks trigger on every new message received in an inbox. To validate them without risk: 1. In the Papo dashboard, go to Settings > Integrations > Webhooks and create a new webhook. 2. Set the trigger — for example, All messages — and in the URL field, paste the temporary Webhook.site address. 3. Save the webhook. 4. Send a test message (via WhatsApp or another connected channel) to the monitored inbox. 5. In Webhook.site, refresh the dashboard and find the newly arrived request. Check the JSON body: it should contain data such as sender number, message content, and conversation ID. 6. If the JSON is empty or malformed, review the chosen trigger and confirm that the message was actually received by the inbox. 7. After validating, edit the webhook and replace the URL with your destination system’s URL. How to test the “Send Webhook” action in Automation Flows Inside the Flow editor, the Send Webhook action lets you trigger data at a specific step in the journey. Test it with a temporarily active flow and a control contact: 1. Build the Flow and add the Send Webhook node at the desired point. 2. In the node configuration panel, fill in the URL with the Webhook.site address, choose the POST method, and build the JSON body using Papo variables such as {{contact.name}} and {{contact.phone}}. 3. Activate the Flow. 4. In the CRM, manually enroll a test contact in this flow (following the same procedure as testing Automation Flows). 5. Monitor the Flow execution history and, at the same time, watch Webhook.site. 6. The received request should show the JSON with the test contact’s real values, replacing the variables. If not, check the body (use "name": "{{contact.name}}" and make sure the contact has the fields filled in). 7. If the request returns a 4xx or 5xx error, check whether the method is correct (usually POST) and whether the Content-Type: application/json header was included. 8. After validation, deactivate the Flow, replace the destination URL with the production URL, and activate it again. Who this process is for - Administrators and system analysts who need to ensure integration integrity before releasing them. - Teams building Flows with webhooks for CRMs, spreadsheets, or automation tools and want to debug the payload without impacting real leads. - Any user who customizes account webhooks and wants to confirm that events are being sent correctly. Frequently asked questions Can I test the webhook without sending a real message? Not for account webhooks, because they are triggered by inbound messages. Use a test WhatsApp number (your own or a colleague’s) to generate the event. For Flows, manually enrolling a control contact allows testing without the lead being a real customer. Is Webhook.site free? Should I use it in production? Yes, Webhook.site generates temporary public URLs and shows traffic in real time, ideal for debugging. Never use these URLs in production — after testing, replace them with your destination system’s URL. The webhook fired but the payload is empty. What should I check? For account webhooks, check the trigger (whether it is capturing the correct message type) and the inbox permissions. For the Flow action, review the variables in the body — fields such as {{contact.name}} will only be filled if the contact has the name field registered. Test with a contact that has complete data. How do I fix 401 (unauthorized) or 403 (forbidden) errors? These errors indicate that the destination system rejected the request. Add an authentication header (for example, Authorization: Bearer your-token) in the Headers field of the webhook configuration, as directed by the external tool’s documentation. Can I test Kanban webhooks the same way? Yes. Webhooks configured in the Kanban module can be tested with a temporary Webhook.site URL — just move a card from one column to another (an action that triggers the event) and inspect the payload in the test dashboard. Do I need to keep the Flow active to test the webhook? Yes. Only Flows with Active status process the webhook node. Activate the flow, run the test, and then deactivate it if necessary. Read also - How to test an automation Flow before activating it - How to send new contact data to Google Sheets via webhook Start for free → With the first user free, you can already create webhooks and test integrations with no commitment.

How to send conversation data to a BI system with webhooks

To forward metadata from conversations that happen in Papo — such as customer name, channel, message text, and assigned agent — to a Business Intelligence tool, use the “Send Webhook” action inside Papo Flows (https://papo.global/). With every new conversation or incoming message, the data is sent automatically to the configured endpoint, feeding your BI with real-time updated information and eliminating the need for manual exports. With this integration, you turn every interaction on WhatsApp, Instagram, email, or another channel into a data point for dashboards, service volume reports, conversion analysis by channel, and much more. Simply configure a Flow with the right trigger and point the webhook to the URL provided by your BI platform or by intermediary tools such as Zapier, Make, n8n, or your own endpoint. | Step | Description | BI example | | :--- | :--- | :--- | | 1. Get the webhook URL | The destination system must provide an HTTP endpoint capable of receiving POST requests with a JSON payload. | URL generated by Power Automate, Zapier, Make, n8n, or the BI tool itself (e.g., REST API). | | 2. Create the Flow in Papo | In the Flows module, build a flow with a trigger that fires when a conversation starts or a message is received. | “New conversation” trigger in the WhatsApp Gold inbox. | | 3. Add the “Send Webhook” action | Enter the destination URL, keep the POST method, and build the request body with the conversation variables. | Payload: {"name": "{{contact.name}}", "channel": "{{inbox.name}}", "text": "{{message.text}}"}. | | 4. Test and activate | Use a test URL (such as Webhook.site) to validate the send before pointing to the real environment. | Check that the fields appear correctly on the receiver and activate the Flow after confirmation. | How it works – step by step 1. Prepare the endpoint in your BI system Papo does not generate the destination URL — you need a service that receives the data and stores it. The main options are: - Automation platform (recommended): Zapier, Make (Integromat), or n8n can create a “Catch Webhook,” generate a unique URL, and then connect the received data to BI (Google Data Studio, Power BI, Tableau) or a database. - Direct BI webhook: some environments, such as Power BI, accept data streaming via API. In this case, you must follow the platform’s instructions to expose an endpoint. - Your own backend: if you have your own API, you can build an endpoint that processes the data and inserts it into your data warehouse. 2. Create the Flow in Papo with the right trigger Go to the Flows module and create a new flow. The most common trigger to feed a BI is “New conversation” — this way, every new contact that reaches an inbox generates a record in your analytics system. You can also use the Message received trigger and configure filters: - All messages: the webhook fires for any interaction. - Specific messages: it only fires when the message contains a certain keyword, came from a specific channel, etc. Select the desired inbox (e.g., WhatsApp, Instagram, email) so that only conversations from that channel are sent. 3. Configure the “Send Webhook” action Add an action node of type Webhook and fill in: - URL: paste the endpoint obtained in step 1. - HTTP method: keep POST. - Body (Payload): define which conversation data will be sent. Use the variables available in the Flow, such as: { "contact_name": "{{contact.name}}", "contact_email": "{{contact.email}}", "source_channel": "{{inbox.name}}", "message_text": "{{message.text}}", "event_date": "{{timestamp}}", "current_agent": "{{agent.name}}" } You can include any variable from the conversation context — check the Flows documentation to see all options. If needed, add headers such as Content-Type: application/json or authentication tokens requested by the destination system. 4. Test and activate the Flow Before putting it into production, run a test: 1. Use a test URL (e.g., Webhook.site) instead of the final URL and trigger a conversation in the configured inbox. 2. Check that the payload arrives correctly, with all expected fields and values. 3. Replace the URL with the final one and activate the Flow. From that moment on, every conversation (or message, depending on the trigger) will fire the webhook automatically. Who this integration is useful for - Data and BI analysts who need to consolidate service metrics without relying on manual CSV exports. - Operations managers who want dashboards with conversation volume by channel, peak hours, and agent workload. - Marketing and sales teams who want to cross-reference conversation data with campaigns and funnels in the CRM. - Companies already using tools such as Power BI, Tableau, or Looker Studio and want to feed dashboards with real data from WhatsApp and other channels. Frequently asked questions (FAQ) What conversation metadata can I send to BI? You can send any variable available in the Flow context, such as contact name, message content, source channel, email, phone number, assigned agent, and date/time. Combining these fields lets you create reports on volume, response time, and lead source. My BI tool does not have a native webhook. How do I integrate it? The simplest way is to use an automation platform (Zapier, Make, n8n). These tools generate a webhook URL, receive data from Papo, and then route it to BI through ready-made connectors or APIs. This way, you do not need to program your own endpoint. Can I filter which conversations generate data sends? Yes. In the Flow trigger, you can choose a specific inbox and configure the “Specific messages” option, defining keywords or other criteria. This way, only interactions that meet the filter fire the webhook. Is the data sent in real time? Yes. The webhook is triggered as soon as the configured event occurs (new conversation or message received), allowing your BI to be updated almost instantly. What happens if the webhook request fails? The Papo Flow logs the error. You can check the Flow execution log to identify failures and, if desired, configure fallback actions (such as sending an alert email) to ensure no critical information is lost. Are there usage limits for webhooks? Flows and Webhook sending features are included in the platform. Specific information about request limits and data volume, if any, is presented on the Papo website or dashboard according to the plan you purchased. Read also - How to send new contact data to Google Sheets via webhook - How to export report metrics to external spreadsheets Start free → Centralize your customer service on WhatsApp and feed custom dashboards with real conversation data, without manual exports.

How to request technical support directly from the Papo platform

To request technical support from Papo (https://papo.global/), you can contact support directly through the platform, gathering essential information such as problem details, screenshots, and conversation logs to speed up diagnosis, without needing to use external channels. When a technical issue arises, every minute spent trying to describe the problem or locate evidence is a minute away from serving your customers. The good news is that Papo offers ways for you to prepare and request the help you need in a centralized way, ensuring your request arrives with enough context for a quick resolution. | Step | Recommended Action | Benefit for Diagnosis | | :--- | :--- | :--- | | 1. Problem Context | Describe what you were doing, in which module, and the expected result versus the one obtained. | Reduces back-and-forth questions to understand the situation. | | 2. Visual Evidence | Capture the entire screen, showing the browser URL and, if possible, the developer console (F12). | Provides visual and technical clues about loading or permission errors. | | 3. Activity Record | Identify specific conversations, campaigns, or contacts affected by the problem. | Allows the support team to trace the incident in logs and account history. | | 4. Account Data | Have the email of the administrator or Papo account holder on hand. | Essential to locate your account and quickly check access permissions. | How to prepare to open a support ticket The first step for effective assistance is to gather the information that contextualizes the problem. This speeds up analysis and prevents you from having to repeat details. When you notice a failure, start documenting it immediately. 1. Identify the affected area: Determine whether the problem is in a specific Inbox (messages not arriving), in Super Chat (AI giving wrong answers), in Kanban (cards not moving), in Trigger (campaign with an error), or in Reports (inconsistent data). 2. Collect the evidence: Take screenshots that show the entire Papo screen, including the browser address bar. If the error is related to the website widget, for example, having the URL of the page where it is installed is crucial. 3. Put together a step-by-step summary: Write down the path you took until the error. Example: "I accessed Conversations, clicked on customer 'João's conversation, tried to open the contact profile, and the screen went blank." 4. Set aside the conversation logs: If it is a problem with a specific interaction, copy the conversation ID or keep the link to that conversation open. This is the most direct clue for the support team to inspect what happened. Where to ask for help in Papo Although the focus is on resolving everything without leaving your workflow, contacting Papo technical support is done through a help request. Specific details about official contact channels and service hours are available on the Papo website and in your account. When you make contact, you will already have all the material gathered using the tips above, which will greatly speed up the solution. Using the Help Center for initial diagnostics Even before opening a ticket, the Papo platform offers resources that can help you resolve common questions or collect the necessary evidence. The Help Center contains articles and tutorials covering a wide range of scenarios. Many configuration questions can be resolved with a quick search. The Reports module is also a great ally. If you suspect that a channel has low delivery or an agent has atypical performance, generating a report of conversations by channel or productivity by agent may be the missing evidence to support your ticket. Frequently Asked Questions Where can I find the link to talk to support? The way to contact Papo technical support is provided in your account and on the official website. With the screenshots and problem details already saved, you will be ready to detail your request as soon as you access the channel. Can I attach files directly to the support ticket? The ability to attach files to a help request is a standard feature expected so that you can send your screenshots and logs. Gather all evidence in a folder before starting contact. What information is essential to resolve my problem faster? The most valuable information is: the account email for Papo, a clear step-by-step description that led to the error, full-screen screenshots, and, if applicable, the ID or link of the problematic conversation. This allows the team to reproduce the scenario and investigate the logs. How can I check whether the problem is general or only in my account? Before contacting support, you can check whether other channels are working normally. If WhatsApp is having problems, test whether the website chat receives messages. If possible, ask a teammate to run the same test. Connection problems with a partner API, such as Instagram, can be checked on that platform's public status sites. How do I track the progress of my ticket? After opening your request, tracking is done through the same channel where you started contact. The Papo support team will keep you updated on the progress of the analysis and the solution found. Read also - How to use Papo without a WhatsApp number: support via website chat and email - How to generate a report of conversations by channel and export the data to CSV Get started for free → Centralize your customer service and have the entire support and CRM structure in the palm of your hand, at no cost for the first user.

How to revoke an active session from your Papo account and increase security

Papo Global (https://papo.global/) brings your account security options together in one place, where you can list active sessions, identify devices that aren't yours, and revoke their access immediately — without relying on support. If someone accessed your account on a shared computer and forgot to sign out, or if you notice an unknown login, revoking a session is the first action to regain control. Flow summary | Action | What to do | Result | |:---|:---|:---| | 1. Access account security | Go to Papo account settings, "Security" section (or equivalent) | View current sessions | | 2. Review sessions | Check device, approximate location, and time for each session | Detect unauthorized access | | 3. Revoke session | Select the suspicious session and end it | The device is logged out immediately | | 4. Strengthen security | Enable two-factor authentication (2FA) and change your password if needed | Prevent new unauthorized access | Why revoking active sessions is essential Each login to Papo creates a session: a token that keeps access without asking for your password every time. While the session is active, anyone with the device can enter your account. Revoking a session interrupts that access immediately, even if the device is now out of your reach. It's immediate protection when you: - Used a public or third-party computer; - Sold, lent, or lost a phone/laptop; - Identify a login from a location or time you don't recognize; - Suspect your credentials were leaked. How session management works in Papo The platform records each active login and displays it in the account security area. There you see: - Device and browser used for the login. - Approximate location (based on IP). - Date and time of the last activity. This makes it easy to distinguish your access from a suspicious one. With one click (or tap), you can drop the unwanted session. The device loses access and, to return, will need a new login with your credentials. This feature is in the same section where you enable two-factor authentication, strengthening the set of protections. Because the interface is updated frequently, the exact screen name may vary; check the Papo Global Help Center for the updated path. Who should monitor active sessions - Account administrators: who manage access for agents and integrations. - Agents who use personal and corporate devices: to ensure only authorized devices keep the session. - Business owners: who concentrate on Papo channels and cannot take risks. Final words on security Revoking sessions is a quick reactive measure. Combine it with enabling 2FA (two-factor authentication) and periodically checking sessions to keep your account locked down without complications. Frequently asked questions What is an active session in Papo? It is a valid connection between your browser/app and the platform, generated after login. While active, the device browses without asking for the password again. Where can I find the active sessions of my account? In the account security area, accessible from your profile settings in Papo. Because menus are updated, check the Help Center for the exact step-by-step. Does revoking a session block the user? No. It only ends that specific session. The device loses access immediately, but the account owner can log in again with the correct password (and 2FA, if enabled). Do I need to do this if I enabled 2FA? Yes. 2FA protects login, but it does not eliminate sessions that are already open. Revoking a session is the complementary action to cut off access that has already occurred. Can I revoke sessions from the mobile app? Session management is generally done through the Papo web dashboard. Check the security section to see if the option is available in the app; interfaces are updated regularly. How many sessions can I have at the same time? There is no hard limit, but you can see how many are active in your account and revoke the ones that are no longer needed. Read also - How to set up two-factor authentication (2FA) in your Papo account — improve login security. - How to request technical assistance directly from the Papo platform — if you need help with access. Start for free and lock down your account → The first user is free so you can test the platform and adjust the security of your WhatsApp service.

How to invite an agent with limited access to only one inbox

To invite an agent with limited access to only one inbox in Papo (https://papo.global/), you need to create a custom role that restricts visible modules and associate the agent exclusively with the team responsible for that inbox, ensuring they see only conversations from that channel. This setup is ideal when you need an external attendant, partner, or outsourced team to access only conversations for a specific customer or department, without seeing other inboxes in the account. Setup summary | Step | What to do | | :--- | :--- | | Custom role | Create a profile that allows access only to the Conversations module (and other essential ones), blocking modules such as Reports, Settings, or Kanban. | | Dedicated team | Create a team containing only the agents who should see that inbox. | | Inbox association | Link the team to the desired inbox instead of adding agents individually. | | Agent invitation | Invite the agent with the custom role and include them in the created team. | How to restrict an agent to a single inbox Papo organizes conversation access through teams and roles. To limit an agent to a specific inbox, you combine these two resources: 1. Custom role – defines which modules the agent can access (e.g., only Conversations, with no access to Reports or Settings). 2. Team linked to the inbox – the agent is placed in a team that is exclusively associated with the inbox they should handle. This way, even if there are other inboxes in the account, the agent will only see conversations from the team they belong to. Step by step 1. Create a custom role with restricted access The custom role lets you control which platform modules the agent sees. For minimal access: - Go to Settings in the side menu. - Scroll to Custom Roles and click Add custom role. - Give it a name (e.g., “Single Inbox Agent”). - In permissions, check only the essential modules for service, such as Conversations. Leave modules such as Reports, Settings, Kanban, or Contacts unchecked as needed. - Save the role. Important: The custom role controls module visibility, but it does not restrict which inboxes appear. Inbox restriction is done by association with a team. 2. Create a dedicated team for the inbox - Still in Settings, go to the Teams section. - Create a new team with a name that identifies the inbox (e.g., “Customer X Support”). - Add to the team only the agents who should access that inbox. If the agent does not exist in the account yet, you can invite them later. 3. Associate the team with the inbox - Go to Settings → Inboxes. - Find the inbox that will be the only one visible to the agent. - Click the inbox Settings and access Collaborators. - Instead of selecting individual agents, choose the team you created. - Save the change. From that moment on, all team members will see only conversations from that inbox. If the agent belongs to more than one team, they will see the inboxes of all teams they are linked to — so keep them in a single team. 4. Invite the agent with the correct role and team - If the agent is not in the account yet, go to Settings → Agents (or Users) and use the Invite agent option. - In the invitation, select the custom role created in step 1. - After the agent accepts the invitation, go to team management and add them to the dedicated team from step 2. If the agent already exists in the account, edit their profile to change the role and make sure they are only in the desired inbox team. Who this setup is useful for - White-label resellers who need to give agents of each end customer access only to their own inbox, without exposing other customers’ data. - Operations with sensitive data (finance, legal) that require total segregation between departments. - Outsourced teams working on a specific project or campaign and who should not access the rest of the operation. - Franchises or units that share the same Papo account but need isolation between each store’s inboxes. Frequently asked questions Can the agent still see the summary of other inboxes? No. The inbox summary (open, resolved, unassigned) is displayed only for inboxes the agent has access to. Since they are linked to a single team, they will see only that inbox’s summary. Can I limit the agent to reading conversations but prevent them from replying? The custom role lets you control modules, but more granular permissions within the Conversations module (such as read-only) are not covered by standard roles. For that level of detail, consult the advanced permission options in the platform documentation. What if the agent is moved to another team by mistake? As long as they are in only one team, they will see only the associated inbox. If they are added to a second team, they will also see the inboxes of that new team. Therefore, periodically review team composition in settings. Does this restriction work for all channels (WhatsApp, email, chat)? Yes. The team + inbox logic is the same for any channel configured in Papo: WhatsApp, Instagram, Facebook, Telegram, email, SMS, or website widget. Do I need to create a custom role for each agent? No. The same role can be assigned to multiple agents. Create a “Restricted Agent” role and reuse it for everyone who should have limited access to a single inbox. Can the agent still access the Contacts or Kanban module? It depends on the permissions you define in the custom role. For maximum restriction, uncheck all modules except Conversations. This way, the agent will not see Contacts, Kanban, Reports, or Settings. See also - How to join Papo Global’s white-label reseller program - How to transfer multiple conversations from an inactive agent to another team member Start for free and set up teams and custom roles → With Papo, you control exactly what each agent sees, keeping the operation organized and each customer’s data isolated.

How to transfer ownership of a Papo account to another admin

To transfer ownership of a Papo account (https://papo.global/) to another admin, the current owner must go to the account settings and start the transfer process. The new owner takes full control, including admin permissions and management of the subscribed plan, while all data, conversations and team settings stay untouched. Changing owners is common in situations such as a change in management, a corporate restructuring, or when the original person in charge leaves the company. Papo lets you make this transition without creating a new account or migrating data manually. Summary of ownership transfer scenarios | Situation | Action required | Impact on the account | | :--- | :--- | :--- | | The current owner leaves the company | Transfer ownership to the new manager before they leave. | None; the account keeps working as usual. | | Merger or acquisition | Adjust the main admin to reflect the new structure. | Permissions and history are preserved. | | Change of technical lead | Hand ownership over to the team's new admin. | The new owner takes over management of the plan and the team. | | White label reseller account | Follow the specific transfer flow for partners. | The reseller keeps the same customer structure. | How the ownership transfer works The process is started by the current owner inside Papo's admin panel. Although the exact steps may vary depending on the account setup, the general flow is: 1. The current owner goes to Account settings and finds the ownership transfer option (usually under Team or General). 2. They start the transfer by entering the new admin's email. The new person in charge must already have a user account on the same Papo account or be registered as a member. 3. The new admin receives a notification and must accept the invitation within a deadline set by the platform. 4. Once accepted, Papo updates the permissions: the former owner loses the highest access level (or remains as a secondary admin, if desired) and the new owner takes full control. During the transfer, all conversations, contacts, automations, inboxes and reports are kept exactly as they were. The team notices no interruption in service. Precautions before transferring - Confirm the new owner's email – typos can delay the process. - Make sure the new admin can access the panel – if they are not yet a member of the account, add them before starting the transfer. - Review billing permissions – the new owner becomes responsible for the plan and any associated charges. - Update contact details – keep a recovery email and a phone number on the new admin's profile for future security checks. Who can request the transfer Only the current owner of the account (the main admin) is allowed to start the process. Members with secondary admin or agent permissions do not have access to this feature. If the original owner is no longer reachable, contact Papo support for specific recovery guidance. Frequently asked questions Can I transfer ownership to someone who is not yet a user on the account? No. The new owner needs an active membership on the Papo account before receiving the transfer. Add them beforehand as a secondary admin and then make the switch. Does the transfer delete any conversation or data? No. All history, tags, contacts, automations and settings stay untouched. Only the highest level of control over the account changes hands. Do I need to cancel the plan and create another one? No. The ownership transfer keeps the same plan, the same WhatsApp number and the same billing structure. You do not have to start from scratch. Does the former owner lose access immediately? It depends on the configuration you choose. After the transfer, the former owner can be kept as an admin or removed, according to the company's needs. How long does the transfer take to complete? The process is immediate as soon as the new owner accepts the invitation. In cases requiring a security check, Papo's team may carry out a brief manual review. What should I do if the current owner no longer has access to their email? If the login email is unreachable, use Papo's support channels to request account recovery, going through identity verification. Read also - How to join the Papo Global white label reseller program - How to revoke an active Papo account session and improve security Start for free now → The first user is free forever, no credit card required.

How to use the Papo API to create and update contacts in bulk

To create and update contacts in bulk programmatically, use the Papo REST API. With secret key authentication (Bearer token) and the account's public key, you can send requests that insert new records or modify existing data in the CRM — ideal for syncing external databases, migrating lists, or keeping records always up to date without manual intervention. The Papo API exposes write endpoints that allow you to create a contact (with name, email, and/or phone) and update an existing contact. Combined with simple authentication and JSON format, these endpoints enable bulk operations when executed in sequence by scripts, automation tools (such as n8n), or custom integrations. Integration process summary | Step | Action | Important detail | | :--- | :--- | :--- | | 1. Get the keys | Generate the secret key (sk_live_…) and copy the public key (pk_live_…) in the Papo dashboard. | The secret key appears only once; store it in a safe place. | | 2. Authenticate calls | Include the header Authorization: Bearer sk_live_… in all write requests. | The public key can be sent in the X-Papo-Public-Key header (optional). | | 3. Prepare the payload | Build a JSON object with the contact fields (name, email, phone, etc.). | Required fields and exact format are in the API documentation. | | 4. Send requests | Make a POST to the creation endpoint or PUT/PATCH for updates. | Each request processes one contact; for many records, automate sending in a loop. | | 5. Check responses | The API returns success: true and the created/updated contact data. | If there is an error, the body includes the code and message for correction. | How authentication and endpoints work Every call that modifies data (creation, update) requires the account's secret key. It must be sent as a Bearer token in the Authorization header or, alternatively, in the X-Papo-Secret-Key header. The public key (fixed per account) can accompany the request in the X-Papo-Public-Key header — its use is optional, but if sent it must match the same account as the secret key. The API base URL is https://app.papo.global/api/v1. From there, the contact endpoints accept the appropriate HTTP verbs to create a new record or modify an existing one. Since the complete documentation details the paths, parameters, and accepted fields, we recommend consulting the official API reference before coding. Authentication example (test request) To validate that your keys are working, you can call the GET /api/v1/me endpoint, which returns the account data. The authentication pattern is the same used in all other endpoints: curl https://app.papo.global/api/v1/me \ -H "Authorization: Bearer sk_live_…" \ -H "X-Papo-Public-Key: pk_live_…" A successful response includes success: true and the data object with the account information. From there, simply replace the endpoint and HTTP method according to the desired operation with contacts. Creating and updating contacts in bulk Although the API processes one contact per request, bulk operation is achieved by executing multiple calls in sequence. A script in Python, Node.js, or an automation in n8n can: 1. Read a list of contacts from a CSV file, database, or ERP. 2. For each record, build the JSON payload with the necessary fields. 3. Send the request to the creation endpoint (if the contact does not exist) or update endpoint (using the contact identifier). 4. Collect the responses and handle any errors (duplicate email, invalid field, etc.). Since the API is REST and uses JSON, any language with HTTP support works. Papo also provides examples in JavaScript and Python on the documentation page, which can be adapted for the contact endpoints. Automatic triggers after creation Whenever a new contact is created via API, the same internal CRM events are triggered. If you have a Flow configured with the “Contact created” trigger, the automation will run automatically — for example, sending a welcome message via WhatsApp or notifying the sales team. This means that API integration not only populates the database but also activates the communication flows already existing in the account. Who this integration is for - Companies migrating from another CRM or spreadsheet that need to import thousands of contacts at once, keeping the Papo database synchronized. - Operations that capture leads in external systems (landing pages, ERPs, e-commerce) and want them to automatically enter the Papo CRM, ready to receive service or campaigns. - IT teams building custom integrations between Papo and internal tools, using the API as a bridge to keep customer data always up to date. - White label resellers who manage multiple accounts and want to automate contact creation at scale for their clients. Frequently asked questions Do I need a secret key to create or update contacts? Yes. All write operations (creation, update) require authentication with the account's secret key. The public key alone does not authorize modifications. Can I send thousands of contacts at once? The API processes one contact per request. For large volumes, you must automate sequential sending, respecting the rate limits described in the official documentation. Do contacts created via API trigger the “Contact created” Flow? Yes. The creation event is the same, regardless of origin. If there is an active Flow with this trigger, it will run for each contact inserted via API. How do I know if a contact already exists to avoid duplicates? You can use the search endpoints (filtering by email or phone) before creating. The API documentation details the available query parameters. Does the API allow updating only some fields of the contact? Yes. In the update request body, send only the fields you want to modify. The others remain unchanged. Where can I find the complete list of endpoints and parameters? The complete reference is available on the API documentation page. There you will find the paths, methods, payloads, and updated examples. Read also - How to automatically trigger a Flow when a new contact is created in the CRM - How to export contacts extracted in the Extractor to CSV and import them into the Papo CRM Start for free and integrate your CRM with Papo via API → With the first user free, you can already generate your API keys and test bulk contact creation at no initial cost.

How to integrate Papo webhooks with Power BI for real-time dashboards

To integrate Papo webhooks (https://papo.global/) with Power BI and create real-time dashboards, Papo offers the Flows module, which triggers webhooks whenever a relevant event occurs in the CRM — such as a new conversation, a contact created, or a closed deal. The data is sent to an intermediate endpoint that stores the events and is then connected to Power BI as a data source, eliminating manual exports and static spreadsheets. Integration overview Papo does not have a direct native connector for Power BI. The integration is done through webhooks: the Flows module captures the event in the CRM and sends it, via HTTP request, to an intermediate destination that you control. This destination can be an online spreadsheet, a database, or an automation platform that accepts webhooks. Power BI reads this source and updates the reports. | Step | Where it happens | What it does | | :--- | :--- | :--- | | 1. Prepare the destination | Intermediate endpoint | Create a receiver that accepts POST and stores the events. | | 2. Create the trigger | Papo (Flows module) | Define the event that starts the sending, such as “Deal Created” or “Contact Created”. | | 3. Configure the webhook | Papo (Flows) | Provide the destination URL, POST method, and JSON body with the event data. | | 4. Feed the source | Intermediate endpoint | Each event becomes a new record in the data source. | | 5. Connect to Power BI | Power BI | Use the source as a dataset and build visual dashboards. | How to export Papo events to a data source The process starts in Papo's Flows module. In it, you create an automation with a trigger and a webhook action. 1. Prepare an endpoint to receive the events The endpoint must accept HTTP POST requests and record each event received. You can use: - A visual automation platform, which generates a webhook URL and lets you map the received fields to a spreadsheet or database. - Your own endpoint, created with a serverless function or script, which processes the request body and inserts the data. In both cases, define in advance the columns or fields that will receive the information, such as name, value, stage, status, date, and funnel. 2. Create the trigger in the Flows module In the Papo panel, access the Flows module and create a new automation. - Trigger: choose the CRM event that should start the sending. The most common for sales dashboards are “Deal Created” and “Contact Created”. - Action: add a Webhook-type step. 3. Configure the webhook action In the webhook action, provide: - URL: the address generated in step 1. - Method: POST. - Body: use JSON with the event fields you want to export, such as name, value, stage, status, funnel, and creation date. After saving and activating the Flow, each new event automatically records a record in the chosen source. This creates a historical base that grows in real time, without manual export. Connecting the source to Power BI With the source populated, open Power BI and use the get data option. Select the connector corresponding to the source you used — for example, the spreadsheet or database connector. Confirm that the columns were identified correctly, especially dates, numbers, and text. After connecting, you can create reports with bar charts, funnels, time series, and tables. Dashboard refresh depends on the source refresh configuration in Power BI. Events continue arriving at the intermediary in real time; the panel will reflect the new records according to the defined interval. Who this integration is useful for - Sales managers who want to track the pipeline and conversion by stage without relying on static spreadsheets. - Operations analysts who need to cross-reference Papo funnel data with other metrics in a single panel. - Marketing teams who want to visualize contact generation and performance by channel. - Customer service operations who monitor conversation volume, response time, and status by inbox. Frequently asked questions Do I need an official Papo connector for Power BI? No. Papo exposes native webhooks and Flows module webhooks. You use an intermediary to receive the events, and Power BI reads that source. There is no automatic native integration between Papo and Power BI. Which events can I capture via webhook? The events available in the Flows module, such as the creation of a deal or a contact. Other events can be configured according to the Flows options in your account. Does the data arrive in Power BI in real time? Webhooks send each event in real time to the intermediate endpoint. Power BI updates the panel according to the refresh frequency configured for the source. For low latency, configure a more frequent refresh or use a source compatible with near real-time refresh. Do I need to know how to program? It depends on the intermediary. Visual automation platforms let you build the flow without code. For your own endpoints, a small script or function may be necessary to process the POST and record the data. Can I use this flow for dashboards from multiple accounts? Yes. Each account can send its events to a separate destination or to the same source with an account identifier. Power BI consolidates the sources into a single management report. Read also - How to customize a productivity report with CSAT and response time metrics Start free with Papo Global → Create your free account and start capturing CRM events with webhooks to build real-time dashboards.

How to use Papo's API to send WhatsApp message templates (HSM)

With Papo (https://papo.global/), you can use the REST API to send approved WhatsApp message templates (HSM), automating transactional notifications and campaigns without accessing the interface. The API allows you to list the Cloud API inboxes in your account, retrieve templates approved by Meta, and send them to one or multiple contacts, as long as you have an API token and the templates are synced in the platform. | API action | What it does | Example use | | :--- | :--- | :--- | | List WhatsApp inboxes | Returns the WhatsApp Cloud API inboxes associated with the account | Select the correct inbox before sending | | List approved templates | Returns the message templates (HSM) with “approved” status for a given inbox | Check the HSMs available for sending | | Send HSM to one contact | Sends an approved template to a single phone number, filling in the variables | Order notification, appointment reminder | | Send HSM to multiple contacts | Sends the same template to a list of contacts at once | Marketing campaign, mass announcement | How HSM sending works via the API The Papo API mirrors the platform's features. To send a WhatsApp message template, you don't need to create anything new via code: templates are created and submitted directly in Meta Business Manager and, once approved, appear automatically in your Papo account. The API only queries the list of approved templates and performs the send. The typical integration flow consists of: 1. Generate an API token in the Papo dashboard. 2. Identify the WhatsApp Cloud API inbox where the template was synced. 3. Get the list of approved templates (HSM) from that inbox. 4. Prepare the request with the necessary parameters: template ID, language, recipient number with country code, and variable values (if the template contains {{1}}, {{2}}, etc.). 5. Send the request — either to a single contact or to a set of numbers, each with its own custom variables. Step by step to use the API 1. Generate an API token In your Papo account settings menu, go to the API or access tokens section. Create a token with the permissions needed to manage conversations and messages. Store the token in a safe place; it will be sent in the header of all requests. 2. List the available WhatsApp inboxes Before sending any template, you need to know which inbox contains the approved templates. Use the endpoint that returns your account's WhatsApp Cloud API inboxes. Note the identifier of the inbox you intend to use — it will be required in the following steps. 3. Check the approved templates (HSM) With the inbox identifier in hand, call the endpoint that lists templates with APPROVED status. The response will bring, for each template, the name, available language, category (Marketing, Utility, or Authentication), and expected parameters. This step is important to confirm that the template is released and to know which variables to fill in. 4. Build the send request The send operation for a single contact basically requires: - The template ID (or name, depending on the implementation). - The template language (for example, pt_BR). - The contact's phone number, including the country code (e.g., 5511999999999). - An object with the variable values, if the template contains placeholders. For batch sending (multiple contacts), the call accepts a list of recipients, each with its number and, optionally, its own variables. The template is the same for everyone. 5. Send and check the response The API returns a synchronous confirmation that the send request was accepted. To track the real delivery status (delivered, read, failed), you can configure an outbound webhook — Papo notifies conversation events in real time. The article about receiving real-time events (listed in “Read also”) explains how to enable this feature. Who should use the API to send HSM Any business that wants to automate transactional communications from external systems benefits from the API. Instead of relying on the Papo interface for each notification, you can integrate sending directly into your ERP, CRM, or e-commerce platform. Common examples: - Purchase confirmation or order status update. - Appointment or scheduling reminder sent 24 hours in advance. - Overdue invoice collection with the payment link. - Flight or reservation change communication. The API is especially useful when the rule that determines when to send the template lives in another software — for example, a logistics system that triggers the delivery notification as soon as the package goes out for transport. Frequently asked questions Does the Papo API have an additional cost? The API is available in Papo plans. You can generate tokens and use the endpoints according to your plan. Details on limits and per-request fees are on the plans page and in the API documentation. Do I need to create message templates via the API? No. Templates must be created and submitted for approval in Meta Business Manager. Once approved, they are automatically synced in Papo and appear in the API template listing. Can I send HSM to numbers that are not in Papo's CRM? Yes. The recipient does not need to be previously registered in the platform's CRM. Just provide the WhatsApp number (with country code and area code) in the request. However, you must have the customer's consent (opt-in) to receive the communication, especially if the template is in the Marketing category. How do I know if the message was delivered? The API's immediate response confirms that the request was accepted and sent to WhatsApp. To monitor failures, deliveries, and reads in real time, you need to enable Papo's event webhook (outbound). See the webhooks guide in the help center. Is there a rate limit for API sends? Yes. Papo applies rate limits to protect service stability and comply with WhatsApp policies. It is recommended to keep moderate speeds — avoiding sudden spikes helps preserve the health of the number. The exact values are in the API documentation. Can I use the API for mass marketing campaigns? Yes, as long as you use only approved templates in the Marketing category and have explicit opt-in from recipients. Sending unwanted messages can generate reports and put your number at risk of being blocked. Plan sends with cadence control and always respect WhatsApp policies. Read also - How to receive real-time events from Papo via Webhook (outbound) - How to use Papo's API to create and update contacts in bulk Start automating your HSM sends now – try it free → Create your Papo account and send approved message templates at no cost for the first user.

How to use the Papo API to create and manage tags

With the Papo REST API, you can list existing tags, create new tags, and apply a tag to a contact with an open conversation — all through authenticated requests, without opening the dashboard. It's a programmatic way to automate the categorization and organization of service from external systems, CRMs, or automation tools. The Papo API exposes Conversation resources that include tag management. With them, your team can maintain a consistent taxonomy, prepare categories before campaigns, and classify contacts and conversations in real time, using the same authentication as other platform endpoints. Summary of tag operations via API | Operation | What it does | When to use | | :--- | :--- | :--- | | List tags | Returns the tags registered in the account, with name and color for visual identification. | Audit account standardization or sync tags with another tool. | | Create tag | Creates a tag in the account without applying it to a contact. | Prepare new categories before applying in bulk or in automations. | | Apply tag to contact + conversation | Creates the tag if it doesn't exist and applies it to the contact and the open conversation. | Automate triage, qualification, or classification as soon as the conversation comes in. | How API authentication works All write routes, including tag operations, require the account's secret key. It must be sent as a Bearer token in the authorization header. The account's public key is optional, but if sent, it must match the same account as the secret key. The API base URL is https://app.papo.global/api/v1. Keys are generated in the developer area of the Papo dashboard. The secret key appears only once upon creation; store it in a safe place and revoke it if there is a suspected leak. How to use it in practice 1. Access the developer/API area in the Papo dashboard and generate a secret key. Also copy the account's public key. 2. In each request, authenticate with the secret key as a Bearer token. If you want to strengthen validation, send the public key in the header indicated in the documentation. 3. To list tags, call the API's tag listing endpoint. The response returns the registered tags, allowing you to map what already exists before creating new ones. 4. To create a tag without applying it, send a JSON payload with the tag information to the creation endpoint. Consult the official documentation for the exact format. 5. To apply a tag to a contact with an open conversation, call the tagging endpoint. If the tag doesn't exist yet, it will be created automatically and applied to the contact and the open conversation. Since the API is REST and uses JSON, any language with HTTP support can be used to integrate tags into scripts, ERPs, CRMs, or automation tools. The official documentation at https://papo.global/pt/docs provides details on authentication, parameters, responses, and code examples. Who this integration makes sense for - Teams that use external automations to classify conversations without opening the Papo interface. - Operations that need to create tags in bulk before campaigns or when implementing a new service taxonomy. - Integrators and white label resellers who connect Papo to client systems and want to maintain consistent categorization across accounts. - Companies that already use the Papo API for contacts and messages and want to complete the flow with tags. Frequently asked questions Do I need to create the tag before applying it via API? No. The API has a feature that creates the tag in the account if it doesn't exist and applies it to the contact and the open conversation. There is also the option to only create the tag, without applying it to any contact. Does the tag applied via API apply to both the contact and the conversation? Yes. The tagging feature applies the tag to the contact and the open conversation, helping to classify both the lead's history and the ongoing service. Is the authentication the same as used in other Papo endpoints? Yes. Write routes require the account's secret key, sent as a Bearer token. The public key is optional and, if sent, must match the same account. Where do I find the exact paths and payload format? In the official API documentation, available at https://papo.global/pt/docs. There you will find details on authentication, parameters, responses, and code examples for tags and other resources. Can I use the API to classify old conversations in bulk? The application feature described in the platform acts on the contact and the open conversation. For specific cases of migration or retroactive classification, it's best to consult the official documentation and combine conversation listing with sequential calls, when the flow allows. Read also - How to use the Papo API to create and update contacts in bulk - How to use the Papo API to send WhatsApp message templates (HSM) Start for free → Create your free account and centralize WhatsApp, Instagram, email, and SMS in a single inbox, with tags to organize your service.

How to use the Papo API to create and update deals in Kanban

To create and update deals in Kanban programmatically, use the Papo REST API. With secret key authentication (Bearer token) and the account's public key, you can send requests that create cards, move opportunities between stages, and mark results, integrating the sales pipeline with external systems without manual intervention. The Papo API exposes write operations for Kanban, allowing you to work with pipelines, stages, and CRM cards. This makes it possible to sync an ERP, a landing page, or a payment tool with the sales pipeline, keeping opportunities always up to date. Summary of the Kanban integration | Step | Action | Important detail | | :--- | :--- | :--- | | 1. Get the keys | Generate the secret key (sk_live_…) and copy the public key (pk_live_…) in the Papo dashboard. | The secret key appears only once; store it in a safe place. | | 2. Authenticate calls | Include the Authorization: Bearer sk_live_… header in all write requests. | The public key can be sent in the X-Papo-Public-Key header (optional). | | 3. Know pipelines and stages | List the Kanban pipelines and their stages to get the required identifiers. | The API response returns the identifiers used in subsequent calls. | | 4. Create or move cards | Send the operation to create a card in a stage, move a contact's card to another stage, or mark a result. | Each operation processes one action; for many records, automate sending in a loop. | | 5. Validate the response | The API returns success: true and the card or listing data. | In case of error, the response body includes a code and message for correction. | What the API lets you do in Kanban With the Kanban endpoints, you can programmatically: - List available pipelines and their stages, with name and position. - List CRM cards. - List all won cards, for closed sales reports. - Create a card in a stage, optionally linked to an existing contact. - Move a contact's card to another stage of the pipeline. - Mark cards as won or lost. - Create a Kanban pipeline with default or custom stages. These operations allow the pipeline to automatically reflect what happens outside Papo, such as a confirmed purchase, a scheduled meeting, or a signup coming from the website. How authentication and calls work Every call that modifies data requires the account's secret key. It must be sent as a Bearer token in the Authorization header or, alternatively, in the X-Papo-Secret-Key header. The public key can accompany the request in the X-Papo-Public-Key header; its use is optional, but if sent, it must match the same account as the secret key. The API base URL is https://app.papo.global/api/v1. From it, the Kanban endpoints accept the appropriate HTTP verbs to create, move, update, and list. Since the complete documentation details the paths, parameters, and accepted fields, we recommend consulting the official API reference before coding. To validate that your keys are working, you can call the GET /api/v1/me endpoint, which returns the account data. The authentication pattern is the same used in the other endpoints: curl https://app.papo.global/api/v1/me \ -H "Authorization: Bearer sk_live_…" \ -H "X-Papo-Public-Key: pk_live_…" The successful response includes success: true and the data object with the account information. Typical integration flow with external systems A script in Python, Node.js, or automation in tools like n8n can execute the full pipeline cycle: 1. List pipelines and stages to get the identifiers for each column. 2. Create a card in the initial stage, linking to a contact if necessary. 3. Move the card to a new stage when an external event occurs — for example, payment confirmed or meeting scheduled. 4. Mark the card as won or lost when the opportunity is completed. 5. List won cards to feed reports, dashboards, or BI systems. Since the API is REST and uses JSON, any language with HTTP support works. Payload details and fields for each operation are in the official documentation. Who this integration is for - Companies that capture opportunities in external systems, such as landing pages, ERPs, or e-commerce, and want them to enter the Papo pipeline automatically. - Operations that need to move cards according to payment events, such as gateways or billing platforms, without opening the CRM manually. - BI and data teams that want to pull won cards and values into real-time dashboards. - IT teams building custom integrations between Papo and internal tools, using the API as a bridge between the sales pipeline and the rest of the operation. Frequently asked questions Do I need to use the public key in all calls? No. The public key is optional, but if sent in the X-Papo-Public-Key header, it must match the same account as the secret key. How do I know which stages exist in my pipeline? List the Kanban pipelines via the API. The response returns the stages of each pipeline with their identifiers, used to create or move cards. Can I create a card already linked to a contact? Yes. Card creation allows optionally linking to an existing contact, keeping the customer's history and data associated with the opportunity. Does the API allow updating a card's value? The API exposes write operations for Kanban cards. The exact fields that can be updated, including values, are detailed in the official API documentation. Is it possible to mark a card as won or lost via the API? Yes. The API allows marking cards as won and lost, in addition to listing all won cards for reports and dashboards. Do I need to program, or can I use automation tools? You can use any language with HTTP support or automation tools like n8n, executing the calls in sequence according to the desired flow. Read also - How to use the Papo API to create and update contacts in bulk - How to receive real-time events from Papo via Webhook (outbound) Start free → The first user is free and does not require a credit card.

How to use the Papo API to manage teams and members

With the Papo REST API, you can automate team administration without opening the dashboard: list teams, create teams, list members of a team, add users to a team, and list or create inboxes. It is the programmatic way to keep your service structure synchronized with external systems, large operations, and white label resellers. The Papo API exposes team and inbox resources with the same authentication as the platform's other endpoints. With them, your team can provision new structures, audit who belongs to each group, and prepare conversation routing without manual intervention in the dashboard. Summary of team and member operations via API | Operation | What it does | When to use | | :--- | :--- | :--- | | List teams | Returns the teams registered in the account. | Audit the structure before creating a new team. | | Create team | Creates a team with a name and optional description. | Provision a new team via script, ERP, or CRM. | | List members of a team | Returns the users who are part of that team. | Check who is included and avoid incorrect access. | | Add users to the team | Includes one or more users by providing comma-separated IDs. | Synchronize the team with the current roster of agents. | | List inboxes | Returns the inboxes with the channel, in the administrator view. | Check available channels and how they are organized. | | Create inbox | Creates a new inbox. | Provision new channels along with the team structure. | How API authentication works Write operations, including team and member operations, require the account's secret key. It must be sent as a Bearer token in the authorization header. The account's public key is optional, but if sent, it must match the same account as the secret key. The API base URL is https://app.papo.global/api/v1. Keys are generated in the developer area of the Papo dashboard. The secret key appears only once at creation; store it in a safe place and revoke it if you suspect a leak. Step by step to manage teams and members via API 1. Go to the developer/API area in the Papo dashboard and generate a secret key. Also copy the account's public key if you want additional validation. 2. In each request, authenticate with the secret key as a Bearer token. If you reinforce validation, send the public key in the header indicated in the documentation. 3. List existing teams to map the current structure before creating new ones. 4. Create a team by sending a JSON payload with a name and, if necessary, a description. Consult the official documentation for the exact format. 5. List the team members to audit who is already included and avoid duplicates. 6. Add users to the team by providing comma-separated IDs. This step synchronizes the team with the current roster of agents. 7. List inboxes with the administrator view to check existing channels and use the API also to create inboxes when necessary. Because the API is REST and uses JSON, any language with HTTP support can be used to integrate teams and members with scripts, ERPs, CRMs, or automation tools. The official documentation at https://papo.global/pt/docs provides details on authentication, parameters, responses, and code examples. Who this integration makes sense for - Large operations that need to create and adjust teams frequently without opening the dashboard manually. - IT and automation teams that synchronize the agent structure with directories, HR, or internal systems. - White label resellers that provision customer accounts in a standardized way, reusing the same team and inbox logic. - Companies that already use the Papo API for contacts and conversations and want to complete the flow with team administration. The API manages the team structure and member inclusion. User roles, such as Agent or Administrator, and granular permissions continue to be defined in the dashboard. By adding a user to a team and connecting them to the relevant inboxes, you control operational access to conversations. Frequently asked questions Does the Papo API define the user role, such as Agent or Administrator? No. The teams and members API focuses on creating teams, listing members, and adding users. Defining each user's role and permissions is done in the dashboard. By including a user in a team and in the correct inboxes, you restrict access to operational conversations. Can I create a team without adding members in the same step? Yes. The API allows you to create a team with a name and optional description, without including users immediately. Later, you can add members using the bulk inclusion operation. How does the API identify the account in requests? By the secret key sent as a Bearer token. The public key is optional and, if sent, must match the same account as the secret key. Does this API work for white label resellers? Yes. Resellers can use the API to provision teams and members in customer accounts in a standardized way, reducing manual configuration and maintaining consistency across operations. Where can I find the exact paths and payload format? In the official API documentation, available at https://papo.global/pt/docs. There you will find details on authentication, parameters, responses, and code examples for teams, members, and other resources. Read also - How to use the Papo API to create and manage tags - How to manage users and permissions within your white label platform Start free and automate teams and members via API → The first user is free forever, so you can validate the integration before structuring your operation.

How to use the Papo API to manage inboxes (connections)

With the Papo REST API, you can list existing inboxes and create new connections for channels such as WhatsApp and Instagram — all through authenticated requests, without opening the dashboard. It is the programmatic way to provision service channels, integrate external systems, and keep your multichannel operation aligned with automation. The Papo API exposes inbox resources that let you check the current configuration and add new channels. This allows IT teams, integrators, and white label resellers to manage connections in bulk, replicate setups between accounts, and automate channel activation without relying on the interface. Summary of inbox operations via API | Operation | What it does | When to use | | :--- | :--- | :--- | | List inboxes | Returns the account's inboxes, with the associated channel (WhatsApp, Instagram, email, etc.) and configuration details. | Audit active channels, sync with monitoring systems, or prepare migrations. | | Create inbox | Creates a new inbox, defining the channel, name, and agents who will have access. | Automatically provision channels when onboarding new clients, units, or brands. | How API authentication works All API calls, including inbox listing, require the account's secret key. It must be sent as a Bearer token in the Authorization header. The account's public key is optional, but if sent, it must match the same account as the secret key. The API base URL is https://app.papo.global/api/v1. Keys are generated in the developer area of the Papo dashboard. The secret key appears only once at creation; store it in a safe place and revoke it if you suspect a leak. To validate authentication, you can call the GET /api/v1/me endpoint, which returns the account data. The authentication pattern is the same used in all other endpoints: curl https://app.papo.global/api/v1/me \ -H "Authorization: Bearer sk_live_…" \ -H "X-Papo-Public-Key: pk_live_…" How to manage inboxes in practice 1. Go to the developer/API area in the Papo dashboard and generate a secret key. Also copy the account's public key. 2. In each request, authenticate with the secret key as a Bearer token. If you want to reinforce validation, send the public key in the X-Papo-Public-Key header. 3. To list inboxes, call the inbox listing endpoint. The response includes each inbox's identifier, the configured channel, and other properties, letting you map what already exists before creating new ones. 4. To create a new inbox, send a JSON payload with the desired channel information — for example, WhatsApp (Meta's official API), Instagram, email, or Telegram. Include the inbox name and the identifiers of the agents who should have access. See the official documentation for the exact format of fields and accepted values. 5. After creation, the inbox is immediately available in the dashboard and starts receiving messages as soon as the channel connection is completed (for channels that require pairing, such as WhatsApp, the API returns the necessary instructions). Because the API is REST and uses JSON, any language with HTTP support can be used to integrate inbox management into scripts, automation tools (such as n8n), or provisioning systems. The official documentation at https://papo.global/pt/docs provides details on authentication, parameters, responses, and code examples. Who this integration makes sense for - IT teams that provision channels in bulk for new units, franchises, or brands, without having to access the dashboard one by one. - White label resellers who want to automate inbox creation for each new client while keeping configuration standardized. - Operations that migrate or replicate configurations between accounts, using listing to audit and creation to mirror channels. - Integrators who connect Papo to external systems for channel management, ensuring the service environment automatically reflects changes. Frequently asked questions Do I need the secret key to list inboxes? Yes. Inbox listing requires authentication with the account's secret key, because it returns sensitive configuration information. The pattern is the same as other API calls: send the Bearer token in the Authorization header. Can I create a WhatsApp inbox via API? Yes. When creating an inbox, you specify the desired channel type — including WhatsApp (Meta's official API) and other supported channels. The payload must follow the expected format for the chosen channel, according to the official documentation. Is it possible to update an existing inbox via the API? The current API allows you to list and create inboxes. To change settings for an existing inbox (such as swapping agents or renaming), you can use the Papo dashboard or, if necessary, recreate the inbox with the new parameters. How do I associate agents with an inbox during creation? In the creation payload, you can provide the identifiers of the agents who should have access to the inbox. These IDs can be obtained through the teams and members API. See the documentation for the exact format. Is authentication the same as used in other Papo endpoints? Yes. All calls that access account resources use the secret key as a Bearer token. The public key is optional and, if sent, must match the same account. Where can I find the exact paths and payload format? In the official API documentation, available at https://papo.global/pt/docs. There you'll find details on authentication, parameters, responses, and code examples for inboxes and other resources. Read also - How to use the Papo API to manage teams and members - How to use the Papo API to create and manage labels (tags) Start automating your connections right now → Create your free account and integrate channels via API without opening the dashboard.

How to use the Papo API to manage automation Flows

With the Papo REST API, you can list all flows available in your account, enable or disable journeys, and enroll contacts in automations programmatically — all through authenticated requests, without opening the panel. It is the way to integrate the flow engine with external systems, n8n workflows, CRMs, or internal scripts. Papo's API exposes flow resources that let you manage automations just as you already manage inboxes or contacts. With it, development teams, integrators, and white label resellers can control in batch which journeys are active, start contacts in sequences, and sync automation status with business processes. Summary of Flow operations via API | Operation | Description | Example use | | :--- | :--- | :--- | | List flows | Returns the available flows and sequences, with identifier, name, type, and status (Active/Inactive). | Audit automations, sync with external dashboards, or check what is running. | | Enable/disable flow | Changes the status of a specific flow, releasing or pausing contact receipt and processing. | Pause a journey during maintenance, release it after adjustments, or disable a completed campaign. | | Enroll contact | Inserts an existing contact at the beginning of an active flow, starting the configured journey. | Include leads from an external CRM, trigger a welcome flow after integration, or correct manual entries. | How API authentication works All API calls, including those involving flows, require the account's secret key. It must be sent as a Bearer token in the Authorization header. The account's public key is optional, but if sent it must match the same account as the secret key. The API base URL is https://app.papo.global/api/v1. Keys are generated in the developer area of the Papo panel. The secret key appears only once at creation; store it in a safe place and revoke it if there is any suspicion of leakage. The authentication pattern is the same used in all endpoints: curl https://app.papo.global/api/v1/me \ -H "Authorization: Bearer sk_live_…" \ -H "X-Papo-Public-Key: pk_live_…" Managing flows via API in practice Although the exact details of each endpoint and parameter are in the official API documentation, the general workflow follows these conceptual steps: 1. Authenticate with the secret key (and, if desired, the public key) to validate the account. 2. List the flows to get the current list of journeys, including their identifiers and status. This lets you map what already exists and choose the right flow for the next operations. 3. Change the status of a specific flow, if needed. Send a request that sets the flow as active (released to receive contacts) or inactive (paused). Only active flows process contacts and accept enrollments. 4. Enroll a contact in an active flow. Provide the contact identifier and the desired flow identifier to insert it at the beginning of the journey. The contact's history in the CRM is preserved. 5. Integrate with external systems — through webhooks or direct calls, you can start contacts coming from an external form, an event in another system, or a data pipeline. The platform also supports creating empty and inactive flows and filling their nodes via API, making it possible to provision complete automations programmatically. For the exact payload formats, required fields, and code examples, see the flows section in the Papo API documentation. Who this integration is for - IT teams that operate multiple automations and need to pause, reactivate, or monitor flows in batch without accessing the panel manually. - White label resellers that want to automatically provision standardized journeys for each new client, enroll initial contacts, and keep alignment across platforms. - Integrators and developers who connect Papo to CRMs, ERPs, or tools such as n8n, triggering flows from external events (a purchase, a signup, a scheduled appointment). - Operations that work with conditional enrollment, where contacts are included in flows only after passing business rules defined in other systems. Frequently asked questions Do I need the secret key to list flows? Yes. Listing flows, like any operation that returns account data, requires authentication with the secret key. The pattern is the same as all other endpoints: send the Bearer token in the Authorization header. Can I enable or disable a flow via API? Yes. The API allows changing a flow's status between active and inactive. You need the flow identifier and the secret key. Inactive flows do not receive contacts and do not advance the journey, even if an enrollment is attempted. How do I enroll a contact in a flow via API? Provide the contact identifier and the active flow identifier in the enrollment call. The contact will be inserted at the beginning of the journey, without deleting conversation history or profile data. The official documentation details the exact parameter format. Is it possible to create a flow from scratch via API? Yes. The API allows you to create an empty flow (with only the Start node) and inactive, as well as fill its nodes with questions, messages, and conditions. This is useful for provisioning automations at scale, especially in reseller or new customer onboarding scenarios. Does the API return the status of each flow when listing? Yes. The listing includes the status (Active or Inactive) of each flow and sequence, plus identifier, name, and type, allowing external systems to monitor what is running and what is paused. Where can I find the complete documentation for flow routes? The official documentation is available at https://papo.global/pt/docs. There you will find all endpoints, accepted parameters, error codes, and examples in multiple languages. The flow routes follow the same REST pattern and authentication as the other modules. Read also - How to use the Papo API to create and update contacts in bulk - How to use the Papo API to create and manage tags Start integrating your flows right now → Create your free Papo account, access the API keys, and connect your automations with the outside world.

How to use the Papo API to manage follow-up Sequences

To manage follow-up Sequences via API in Papo, you can list the available cadences, enroll contacts, and pause a lead’s participation using custom attribute updates — all through authenticated requests, without opening the dashboard. This is how you integrate lead nurturing with CRMs, ERPs, and external automation workflows. Summary of API operations | Operation | Description | How the API performs it | | :--- | :--- | :--- | | List sequences | Get all follow-up cadences in the account, with name, identifier, and status (active/inactive). | Authenticated GET request to the flows endpoint, filtering by the "sequence" type. | | Enroll contact | Insert an existing contact into an active sequence, starting the message journey. | POST with the contact ID and sequence ID to the enrollment endpoint. | | Pause cadence for a contact | Temporarily stop sends to a lead without removing them from the sequence. | Update the contact’s custom attribute (e.g., status_pausa) via the contacts API, combined with a condition in the Flow. | How authentication and endpoints work All operations use Papo’s REST API, authenticated with the account’s secret key (Bearer token). The base URL is https://app.papo.global/api/v1. Keys are generated in the dashboard, in the developer area. Sequence resources are grouped under the flows endpoints. The API allows you to list all flows, including those of the "sequence" type, and also activate/deactivate an entire flow. To enroll a contact, there is a specific endpoint that receives the contact identifier and the flow identifier. The exact details of each endpoint (parameters, payloads, and examples) are available in Papo’s official API documentation. Here, we focus on the workflow for managing follow-up sequences. Step by step: list, enroll, and pause 1. List the available sequences Before enrolling leads, you need to know which sequences exist and their identifiers. The list call returns a relation with name, ID, and status (active/inactive). Only active sequences accept new enrollments. With the list in hand, your external system can map which sequence to use for each lead. 2. Enroll a contact in a sequence With the contact ID (obtained via search or creation through the contacts API) and the active sequence ID, you send a request to insert the contact at the start of the journey. The contact must exist in Papo’s CRM; otherwise, create it first using the contacts endpoint. Enrollment immediately starts sending the scheduled messages, respecting the intervals configured in the Flow. The contact’s history is preserved. 3. Pause the cadence for a specific contact Papo’s API does not have a direct command to "pause" a contact’s participation in a sequence. However, you can achieve the same effect by combining the contacts API with a condition in the Flow. Prerequisite: the sequence must have been built with a condition node that checks a custom attribute (e.g., status_pausa). If the attribute equals "paused", the condition blocks sending the next messages; otherwise, it allows them. (See the article on temporary pause for details on setting up the Flow.) With this structure in the Flow, pausing is done in two steps via API: 1. Identify the contact by ID or search for them by phone/email using the contacts listing endpoint. 2. Update the contact’s custom attribute to "paused" (or the value your condition expects). Use the contact update endpoint, sending the custom field. From that moment on, when the flow reaches the condition, it will identify the "paused" value and will not send the message. To resume, simply update the attribute to any other value (e.g., "active") or clear it, and the contact will continue where they left off. This method keeps the contact enrolled and the progress in the cadence, without losing history. Who this integration is useful for - SDR and B2B sales operations that trigger sequences from external events (e.g., a lead downloaded a resource, a deal was created in the CRM). - White label resellers that automatically provision follow-up journeys for new customers, enrolling initial contacts without manual action. - Marketing and automation teams that use tools like n8n or Zapier to connect Papo to dozens of systems and need granular control over cadences. - Companies with conditional pause processes, where a lead asks for time and the salesperson wants to interrupt the sequence without losing the cadence point — all triggered by a button in the external CRM. Frequently asked questions Do I need the secret key to list sequences? Yes. Every operation that returns account data requires authentication with the secret key, sent as a Bearer token in the Authorization header. Can I enroll a contact that does not yet exist in Papo? No. The contact must exist in Papo’s CRM. You can create it first via the contacts API (with name, phone, or email) and then enroll it in the sequence. Does the API allow removing a contact from the sequence? Removal (canceling enrollment) is not available as a specific endpoint in the current version. The alternative for stopping sends is to pause via a custom attribute, as described, or to deactivate the entire flow, which affects all contacts. How do I know whether the pause by attribute worked? After updating the attribute, the sequence will continue processing the wait nodes. When it reaches the condition, it will check the value. If it is "paused", the message will not be sent. You can confirm in the contact profile, in the Contacts module, that the contact remains enrolled, but the next messages are not triggered. Can I pause the entire sequence via API? Yes. The API allows you to change a flow’s status to inactive, pausing the sequence for all contacts. Use the flow activation/deactivation endpoint. To resume, simply reactivate it. Where can I find the exact endpoints and code examples? The complete API documentation is available at https://papo.global/pt/docs. There you will find the flows and contacts endpoints and the request formats. Read also - How to use the Papo API to manage automation Flows - How to use the Papo API to create and update contacts in bulk Start for free and automate your sequences → With the Papo API, you integrate lead nurturing directly into your stack, without opening the dashboard — the first user is free for you to test.

How to use the Papo API to manage Appointments (scheduling)

Yes, you can manage services, schedules, and appointments via API using the Papo Appointments module. The REST API allows you to list services, professionals, and patients, check the calendar, and create new appointments programmatically, integrating the entire booking flow into your website, app, or external system. The Papo Appointments module is designed to be the control center of your calendar. It organizes four pillars: the services you offer (with name, duration, and price), the professionals who perform them, each one's availability, and the appointments made. With the API, you can automate these operations without manually accessing the panel, maintaining a seamless integration between Papo and your other tools. Summary of Appointments operations via API | Operation | What it does | When to use | | :--- | :--- | :--- | | List services | Returns the registered appointment services, with duration and price. | Sync the service catalog with your website or app so the customer sees the options in real time. | | List professionals | Returns the list of attendants or team members who perform the services. | Display available professionals and their specialties in an external scheduling interface. | | List patients | Returns the registered patients, with name, phone, and ID. | Check if a client already exists in the CRM before creating a new appointment or linking it to an existing record. | | List appointments | Returns appointments filtered by status (e.g., confirmed, pending). | Audit bookings, integrate with reporting systems, or check calendar occupancy before offering new time slots. | | Schedule an appointment | Creates a real appointment in a professional's calendar, for a specific service and patient. | Allow customers to book directly through your website or app, or automate the creation of bookings from external systems. | How API authentication works All write operations in Appointments require your Papo account's secret key, sent as a Bearer token in the authorization header. The account's public key is optional, but if sent, it must match the same account as the secret key. The API base URL is https://app.papo.global/api/v1. Keys are generated in the developer area of the Papo panel. The secret key is displayed only once upon creation; store it in a safe place and revoke it immediately if there is any suspicion of leakage. How to use it in practice 1. Access the developer/API area in the Papo panel and generate a secret key. Also copy the account's public key. 2. In each request, authenticate with the secret key as a Bearer token. If you want to strengthen validation, send the public key in the header indicated in the documentation. 3. To build the scheduling interface, first list the available services and professionals. This way, you can dynamically populate the options on your website or app with real data from your Papo account. 4. To create an appointment, call the appointment creation endpoint, sending in the JSON payload the identifiers of the service, professional, patient, and the desired date/time. The API will validate availability in the calendar configured in the Appointments module and create the commitment. 5. Consult the official documentation at https://papo.global/pt/docs to get the exact paths, required parameters, and code examples. All responses are in JSON format. The API also allows you to list existing appointments with a status filter. This is useful for building tracking dashboards, sending automatic reminders, or integrating appointment status with other systems. Who this integration is for - Clinics, medical offices, and beauty salons that want to offer online scheduling on their own website, with real-time availability. - SaaS platforms and marketplaces that need to connect service providers' calendars to an external booking system. - White label resellers who create customized solutions for end clients and want to expose the Appointments module via API. - Companies with automated workflows that trigger appointment creation from events in CRMs, ERPs, or automation tools. Frequently asked questions Do I need to have the Appointments module configured to use the API? Yes. The services, professionals, and their availability must already be registered in the Papo Appointments module so that the API can list them and validate appointments. Does the API allow creating a new service or professional? The API resources focus on listing existing services and professionals and scheduling appointments. To create or edit services and professionals, use the Papo panel. How does the API know if a time slot is free? When sending a request to schedule an appointment, the Papo API checks the availability configured for the professional and the chosen service on that day and time. If there is a conflict, the appointment will not be created and the API will return an error. Can I use the API to schedule an appointment on behalf of a patient who is not yet in the CRM? You can first use the Papo Contacts API to create the patient (with name, email, and/or phone) and then use the returned ID to create the appointment. Consult the documentation for the contact creation endpoint. Can Papo's AI schedule automatically via API? Papo's Artificial Intelligence, such as Super Chat, schedules directly through the WhatsApp conversation, checking the Appointments module calendar. The API is the path for external programmatic integrations, such as an online scheduling system. Where can I see the exact payload format for scheduling? In the official API documentation, at https://papo.global/pt/docs. There you will find authentication details, parameters, responses, and code examples for the Appointments resources. Read also - How to use the Papo API to create and update contacts in bulk - How to use the Papo API to create and manage tags Start integrating your calendar via API → Sign up for Papo and get access to the REST API to automate your appointments from the first user.

How to receive alerts for new conversations on Telegram

To receive a Telegram notification every time a customer starts a conversation in a specific inbox in Papo (https://papo.global/), you must configure a Flow that triggers a Webhook to an intermediary service that forwards the message to the desired chat. This keeps your support or sales team alert in real time, without having to constantly monitor the platform. Papo does not send the message directly to Telegram. What it does is trigger a Webhook with the data of the new conversation. An intermediary — such as an automation in Make, n8n, a custom script, or a serverless endpoint — receives that Webhook and calls the Telegram API to deliver the alert to the chosen chat. | Step | Action | Tool | | :--- | :--- | :--- | | 1. Prepare Telegram | Create a bot and get the access token and the destination chat ID | BotFather, Telegram | | 2. Configure the intermediary | Create an endpoint that receives the Papo Webhook and sends the message via the Telegram API | Automation service or custom code | | 3. Create the Flow in Papo | Configure a new flow with the “New conversation” trigger and the “Webhook” action pointing to the endpoint | Flows module (Papo) | | 4. Test the notification | Start a conversation in the chosen inbox and check that the message arrives in the Telegram chat | Papo + Telegram | How it works — step by step 1. Prepare Telegram Before anything else, you need a bot on Telegram and the ID of the chat that will receive the alerts. Talk to @BotFather on Telegram to create a new bot and get the access token (something like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11). Then add the bot to the desired group or channel and get the chat_id. A simple way is to send a message to the bot and access https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates to capture the ID. Note down the token and chat_id — they will be used by the intermediary. 2. Configure the intermediary You need an endpoint that receives the Papo Webhook and calls the Telegram API. It can be an automation in Make (Integromat), a workflow in n8n, a serverless function (AWS Lambda, Cloudflare Workers), or a script on your server. The endpoint must: - Accept POST requests with the payload sent by Papo. - Extract the relevant information (contact name, message text, inbox). - Build a call to https://api.telegram.org/bot<TOKEN>/sendMessage with the chat_id and text parameters. Example payload that the intermediary may receive from Papo: { "contact_name": "{{contact.name}}", "message_text": "{{message.text}}", "inbox_name": "{{inbox.name}}" } With this data, the intermediary sends Telegram a message such as: “New conversation from Maria Silva in the WhatsApp Sales inbox: ‘I want to schedule a demo’”. 3. Create the Flow in Papo In the Papo dashboard, go to the Flows module and create a new flow. Give it a name that identifies the alert, such as “Telegram Notification – New conversations”. Add a Trigger node and define that the flow will start when a New conversation arrives. Choose the specific inbox (for example, the connected WhatsApp, Instagram, or Telegram number) that should generate the alert. After the trigger, insert an Action node and select Send Webhook. Fill in: - URL: paste the URL of the endpoint created in step 2. - Method: keep it as POST. - Payload: build the JSON with the variables available in the conversation context, such as {{contact.name}}, {{message.text}}, and {{inbox.name}}. The intermediary will use these fields to compose the Telegram message. 4. Activate and test the flow Save and activate the flow. To test, send a message to the configured inbox — for example, talk to your own WhatsApp number connected to Papo. Within a few seconds, the notification should appear in the Telegram chat. If it does not arrive, check: - Whether the flow is active and the execution log in the Flows module does not show errors. - Whether the intermediary is receiving the request and calling the Telegram API correctly. - Whether the Telegram token and chat_id are valid. Who this integration is useful for - Support teams that use Telegram as their communication hub and need immediate alerts about new tickets. - Sales teams that monitor incoming leads in specific channels, such as a campaign WhatsApp inbox. - Operations teams that want to consolidate notifications from multiple channels into a single Telegram group, without switching between tabs. - Managers who track the volume of new conversations in real time directly in the messenger. Frequently asked questions Do I need a bot on Telegram to receive the alerts? Yes. You need to create a bot via @BotFather and get the access token. The bot will be responsible for sending messages to the chat (group, channel, or private conversation) that you define. Can I send notifications to a Telegram group? Yes. Just add the bot to the group and get the group chat_id (usually a negative number). The intermediary must use that chat_id in the Telegram API call. What should I do if the notification does not arrive on Telegram? Check the Flow execution in the Papo Flows module. If the Webhook was triggered successfully, the problem may be in the intermediary: check whether it received the request and whether the Telegram API call returned an error. Test the endpoint manually with a sample payload. Can I choose which inboxes generate the alerts? Yes. In the New conversation trigger, you define the specific inbox that will be monitored. To notify different inboxes in different chats, create a separate flow for each inbox and point it to the corresponding endpoint. How do I test the integration without disturbing the team? Use a test contact — for example, your own personal number — and send a message to the configured inbox. Confirm that the alert appears only in the test chat. You can delete the test flow after validating. Is there an additional cost for using Webhooks in Papo? Flows and Webhook sending features are included in Papo plans. Detailed information about limits and subscriptions is available on the official website. Read also - How to receive real-time events from Papo via Webhook (outbound) - How to use the Papo API to manage automation Flows Start for free → Create your free Papo account and start receiving Telegram alerts today.

How to Integrate Papo with Microsoft Teams

To receive a notification in Microsoft Teams every time a customer starts a conversation in a specific inbox in Papo (https://papo.global/), you must configure a Flow that triggers a Webhook to a Teams incoming connector. This keeps your support or sales team alert in real time, without needing to constantly monitor the platform. The integration uses Microsoft Teams Incoming Webhooks and Papo Flows to turn a new conversation into an instant alert. Without complex code, you choose the inbox, customize the message content, and ensure no one misses an important lead or ticket. | Step | Action | Tool | | :--- | :--- | :--- | | 1. Prepare Teams | Create an Incoming Webhook in the desired channel and get the send URL | Microsoft Teams | | 2. Create the Flow in Papo | Configure a new flow with the “New conversation” trigger and the “Webhook” action | Flows module (Papo) | | 3. Test the notification | Start a conversation in the chosen inbox and check that the message arrives in the Teams channel | Papo + Teams | How it works — step by step 1. Get the Webhook URL in Microsoft Teams In the Teams channel where you want to receive alerts, click … (more options) and select Connectors. Search for Incoming Webhook and add it. Configure a name (e.g., “Papo Alerts”) and, if desired, an image. Copy the generated URL — it will be used in the Papo Flow. 2. Create a new Flow in Papo In the Papo dashboard, go to the Flows module and create a new flow. Give it a name that identifies the notification, such as “New conversation alert in Teams”. 3. Configure the trigger Add a Trigger node and define that the flow should start when a New conversation arrives. Choose the specific inbox (for example, the WhatsApp number, Instagram, or another connected channel) that should generate the alert. You can filter by message type or channel, depending on your support structure. 4. Add the Webhook action After the trigger, insert an Action node and select Send Webhook (or the equivalent option available in the Flows module). Fill in the main fields: - URL: paste the Teams connector URL obtained in step 1. - Method: keep it as POST. - Payload: define the content that will be sent. Teams accepts a simple JSON with the text field or an Adaptive Card. Example of a simple payload with conversation variables: { "text": "New conversation from {{contact.name}} in inbox {{inbox.name}}: {{message.text}}" } You can use variables such as {{contact.name}}, {{message.text}}, and {{inbox.name}} to customize the message. For a richer card, see the Teams Adaptive Cards documentation and build the corresponding JSON. 5. Activate the Flow and test Save and activate the flow. To test, send a message to the configured inbox — for example, talk to your own WhatsApp number connected to Papo. Within seconds, the notification should appear in the Teams channel. If it doesn't arrive, check: - Whether the flow is active and the execution log in the Flows module shows no errors. - Whether the webhook URL is correct and accessible. - Whether the payload is in the format accepted by Teams (plain text or a valid Adaptive Card). Who this integration is useful for - Support teams that use Microsoft Teams as their communication hub and need immediate alerts about new tickets. - Sales teams that monitor incoming leads in specific channels, such as a campaign WhatsApp inbox. - Operations with multiple channels that want to consolidate notifications in one place, without switching between tabs. - Managers who track the volume of new conversations in real time directly in the Teams corporate environment. Frequently asked questions Do I need to have an incoming connector configured in Teams before using the Flow? Yes. You need to add the “Incoming Webhook” connector to the desired channel and copy the generated URL. This procedure is done directly in Microsoft Teams, outside Papo. Can I send the exact content of the customer's message in the alert? Absolutely. Inside the payload of the Webhook action, you can include dynamic variables such as the conversation text, contact name, and channel, building a rich, contextual notification. Teams accepts both plain text and formatted cards. What happens if the request to Teams fails? The Flow will log the error. You can add failure handling actions, such as sending an email or creating an internal task, to ensure the team does not miss the critical alert. Is it possible to send notifications to different Teams channels depending on the inbox? Yes. Simply create a separate Flow for each inbox and point it to the connector URL of the desired Teams channel. This way, support conversations go to one channel, and sales leads to another. How do I test without disturbing the team? After activating the flow, use a test contact — such as your own personal number — and send a message to the configured inbox. Confirm that the notification appears only in the designated channel. You can delete the test flow after validating. Is there an additional cost to use Webhooks in Papo? The Flows and Webhook sending features are included in Papo plans. Detailed information about limits and subscriptions is available on the website. Read also - How to receive real-time events from Papo via Webhook (outbound) - Automation Rules vs. Flows: when to use each feature in Papo Start for free and integrate your notifications → With Papo, you connect your channels, automate alerts, and start serving customers in minutes — with no initial cost.

How to send new conversation notifications to Discord

To receive a notification in Discord every time a customer starts a conversation in a specific inbox in Papo (https://papo.global/), you must configure a Flow that triggers a Webhook directly to the desired channel on the Discord server. This keeps your support or sales team alerted in real time, without needing to constantly monitor the platform. The integration uses Discord's native Webhooks and Papo's Flows module to turn a new conversation into an instant alert. With no complex code, you choose the inbox, customize the message content, and ensure no one misses an important lead or ticket. | Step | Action | Tool | | :--- | :--- | :--- | | 1. Get the Webhook URL in Discord | Create a Webhook in the Discord server channel and copy the URL | Discord Server Settings | | 2. Create the Flow in Papo | Configure a new flow with the “New conversation” trigger and the “Webhook” action | Flows module (Papo) | | 3. Test the notification | Start a conversation in the chosen inbox and check that the message arrives in the Discord channel | Papo + Discord | How it works — step by step 1. Get the Webhook URL in Discord In Discord, open Server Settings where you want to receive notifications. Go to the Integrations section and select Webhooks. Create a new webhook, choose the destination channel, and copy the full URL generated. It will have the format https://discord.com/api/webhooks/…. Save this URL — it will be used in the Papo Flow. 2. Create a new Flow in Papo In the Papo dashboard, go to the Flows module and click to create a new flow. Give it a name that identifies the notification, such as “New conversation alert in Discord”. 3. Configure the trigger Add a Trigger node and define that the flow should start when a New conversation arrives. Choose the specific inbox (for example, the WhatsApp number, Instagram, or another connected channel) that should generate the alert. This avoids noise and notifies only the inboxes that matter. 4. Add the Webhook action After the trigger, insert an Action node and select the Send Webhook option (or similar). In the configuration field: - URL: paste the Discord Webhook URL obtained in step 1. - Method: keep it as POST. - Payload: define the content that will be sent. Discord expects a JSON with the content field. You can use variables available in the conversation context to customize the alert. Example: { "content": "New conversation from {{contact.name}} in the inbox {{inbox.name}}: {{message.text}}" } The variables will be replaced with the real data at the time of triggering. Optionally, you can include fields such as username and avatar_url to customize the message appearance in Discord. 5. Activate and test the flow Save and activate the flow. To test, send a message to the configured inbox — for example, talk to your own WhatsApp number connected to Papo. Within a few seconds, the notification should appear in the selected Discord channel. If it does not arrive, check: - Whether the flow is active and the execution log in the Flows module shows no errors. - Whether the Discord Webhook URL is correct and has not expired. Who this integration is useful for - Support teams that use Discord as their communication hub and need immediate alerts about new tickets. - Sales teams that monitor incoming leads in specific channels, such as a campaign WhatsApp inbox. - Operations with multiple inboxes that want to consolidate notifications in different Discord channels according to the conversation source. - Communities or internal servers where members need to be notified as soon as a customer gets in touch. Frequently asked questions Do I need administrator permission on the Discord server to create a Webhook? Yes, you need “Manage Webhooks” permission on the Discord server. Usually, server administrators can create the Webhook. If you do not have this permission, ask the administrator to create the URL for you. Can I send notifications to different Discord channels depending on the inbox? Yes. Simply create a separate Flow for each inbox and point it to the Webhook URL of the desired Discord channel. This way, support conversations go to one channel, and sales leads to another, for example. Which variables can I use in the Payload to customize the message? You can use the variables available in the conversation context, such as {{contact.name}} (contact name), {{message.text}} (message text), and {{inbox.name}} (inbox name). Other variables can be checked in the variables documentation for the Flows module. How do I test without bothering the team? After activating the flow, use a test contact — such as your own personal number — and send a message to the configured inbox. Confirm that the notification appears only in the designated channel. You can deactivate the test flow after validating. Does Discord have a request limit for Webhooks? Yes, Discord imposes rate limits to prevent abuse. For a normal volume of new conversations, it is unlikely that the limit will be reached. If your operation generates thousands of alerts in short intervals, consult Discord's documentation on Webhook limits. Are the Flows and Webhooks features included in Papo plans? Yes. The Flows and Webhook sending features are included in Papo plans. Detailed information about limits and subscriptions is available on the website. Read also - How to receive new conversation alerts on Telegram - How to use the Papo API to manage automation Flows Start for free and integrate your channels → Connect WhatsApp, Instagram, and all your channels in a single dashboard, with AI that responds in seconds and alerts that keep your team synchronized in real time.

How to set up Single Sign-On (SSO) to access Papo with Google or Microsoft

To set up Single Sign-On (SSO) in Papo (https://papo.global/), use social login via OAuth in the admin panel and connect your team's identity provider, such as Google or Microsoft. This lets users sign in to the platform with the corporate credentials they already use, without creating another password. The exact authorization steps and available options appear in the account settings area; check Papo's help center for the current path. SSO reduces friction in daily access, cuts down on password-related tickets, and helps administrators keep centralized control of the team. Instead of managing yet another set of credentials per agent, the operation relies on the same login used in Google Workspace or Microsoft 365. | Step | What to do | Goal | | :--- | :--- | :--- | | 1. Open the account settings | Access the Papo admin panel | Find the access and security options | | 2. Choose the OAuth provider | Select Google or Microsoft as the identity provider | Define which corporate login will be accepted | | 3. Authorize the integration | Review the permissions requested by the provider | Connect the company account securely | | 4. Test access | Log out and sign in with the corporate account | Confirm that the SSO flow is active | What Single Sign-On with OAuth is Single Sign-On is an authentication method in which the user signs in once with an identity provider and then accesses different systems without typing new credentials. In Papo's case, social login via OAuth lets the platform confirm the user's identity with Google or Microsoft, instead of keeping its own password database for that access. In practice, the agent clicks the option to sign in with Google or Microsoft, logs in to the provider, and authorizes Papo to use the basic identification data. After that, access is granted to the account linked to the corporate email. How social login works in Papo The flow follows the OAuth standard, without Papo needing to store the provider's password: 1. Login start: the user chooses to sign in with Google or Microsoft. 2. Authentication with the provider: Google or Microsoft validates the corporate credentials. 3. Authorization: the provider asks whether the user agrees to share the necessary information with Papo. 4. Confirmation: Papo receives the confirmation and grants access to the panel according to that user's permissions. The administrator remains responsible for defining which agents can access the operation, which inboxes each one sees, and which modules are available. When it makes sense to enable SSO in Papo Social login via OAuth is especially useful for: - Teams that already work in Google Workspace or Microsoft 365. - Operations with many agents and frequent turnover. - Companies that need more control over who accesses customer service. - Administrators who want to reduce internal password recovery tickets. If your team doesn't yet use one of these providers in a standardized way, it may be better to first organize corporate emails and user permissions. What to prepare before enabling it Before setting up SSO, check these points: - Standardized corporate emails: social login links access to the Google or Microsoft email. Personal emails may fall outside the intended flow. - An available administrator account: keep at least one working administrator access before testing authentication changes. - Team permissions: define which agents will have access to the panel and which inboxes they will be able to handle. - Up-to-date documentation: since Papo's interface can change frequently, check the help center or the official website for the exact screen names and provider requirements. We don't reproduce here clicks or menu paths that aren't documented in the reference materials provided. Papo Global keeps the access and security options in the account settings area. Frequently asked questions Is SSO with Google or Microsoft available on any account? Availability may vary depending on the account type and plan permissions. Confirm in your Papo account's admin area or on the official website whether social login is enabled for your operation. Do I need a Google Workspace or Microsoft 365 account to use it? Usually, social login requires an account with these providers. Without a corporate identity in Google or Microsoft, the provider can't authenticate the user to grant SSO. Does SSO remove the need for a password in Papo? For the user who signs in with Google or Microsoft, yes: the credential becomes the provider's. Administrator accounts and emergency access should be kept and tested to avoid lockouts. Can email and password login be kept at the same time? In many deployments, traditional login and SSO can coexist while the team migrates. Ideally, test both flows before enabling SSO for all users. What should I do if the social login option doesn't appear? Check whether the account has administrator permission and whether the integration with the provider was authorized in the panel. To see the current screens and requirements, check the Papo Global help center. Does SSO apply to customers chatting on WhatsApp? No. SSO is an internal access feature for panel agents and administrators. Customers continue to be served as usual through the connected channels, such as WhatsApp, Instagram, and email, without needing to sign in to Papo. Read also - How to integrate Papo with Microsoft Teams - How to manage users and permissions within your white label platform Start for free on Papo Global → Create your account to centralize channels, CRM, and AI in a single panel.

How to Search and Filter Files in Papo's File Center

Papo's File Center (https://papo.global/) allows you to locate any document, image, or audio in seconds using search by name, folder, and context, plus filters that organize files shared in conversations. | Feature | Description | | :--- | :--- | | Search by name | Type part of the file name and see instant results. | | Filter by folder | Navigate the folder structure to restrict the search to a specific directory. | | Search by context | Find files associated with conversations, AI assistants, or campaigns. | | Folder listing | View all folders with the file count in each one without opening them. | | Metadata | Check details such as type, size, and upload date of any file. | How search and filters work The File Center works as a corporate drive integrated with all Papo modules. Every file uploaded — whether a contract PDF, a product image, or a customer service audio — is automatically indexed. Search scans names, metadata, and context links, while filters allow you to refine results by folder or by association with a platform resource (such as an AI assistant or a specific conversation). When you search for a term, the platform returns all files whose name or metadata match, regardless of where they are stored. If you are inside a folder, the search automatically limits itself to that directory, speeding up location in structures with many items. Step by step to search and filter files 1. Access the File Center – Usually available in the main menu or account settings, in the resource management section. 2. Use the search bar – Type the file name, part of it, or a keyword. Results appear listed in real time. 3. Filter by folder – Select a folder in the directory tree before searching or navigate to it. The search will display only the files contained there. 4. Search by context – Use the available filters (such as "Source" or "Associated with") to find files linked to an AI assistant, a conversation, or a campaign. This way you can quickly locate, for example, the manual that is feeding Capitão or the audio of a specific call. 5. Check the metadata – Click on a file to see type, size, upload date, and other information that helps confirm it's the right item. Who it's useful for These features are essential for teams that deal with a large volume of documents and need agility in their daily work: - Support and customer service: find contracts, terms, and manuals in seconds during a conversation. - Sales: locate proposals, catalogs, and support materials without leaving the service flow. - Marketing: retrieve campaign pieces, images, and audio for reuse or adjustments. - AI operations: manage the documents that train Capitão and quickly check which files are associated with each knowledge base. Frequently Asked Questions (FAQ) Does the File Center search differentiate between uppercase and lowercase? No. The search is case-insensitive, so you can type "contract" or "Contract" and get the same results. Can I search for files by type, such as PDF or image? Yes. You can type the extension (e.g., ".pdf") in the search bar or, if the interface offers it, use file type filters to restrict results. Do search results include files from all folders? By default, the global search scans the entire File Center. If you are inside a specific folder, the search automatically restricts itself to that directory. How do I find a file that was attached to a specific conversation? Use the search by context or the "Associated with conversation" filter (when available) to list only files linked to a specific contact or service. Does the search also locate files used to train Capitão? Yes. Files added to the AI knowledge base are indexed and can be found by search, usually with a context marker indicating that association. Is it possible to see how many files exist in each folder without opening them? Yes. The folder view displays the file count next to each directory name, making navigation easier. Read also - What is the AI Knowledge Base and how to add documents to train Capitão Start now for free → Centralize your documents and find any file in seconds, with the first user free.

How to manage your subscription, plan, and payments on Papo

On Papo (https://papo.global/), you manage your subscription, plan, and payments in the payments area of your account. There you can check the plan and credit summary, access the billing portal to update your card and download invoices, and generate a checkout link to top up credits used by features such as Disparador. Keeping this administrative side under control avoids service interruptions, especially for those using WhatsApp, campaigns, and multiple agents. Papo brings financial information together in one place, without relying on spreadsheets or manual charges. Financial management summary | Resource | What it allows | When to use | | :--- | :--- | :--- | | Subscription summary | Shows the current plan, credit, and billing status | To check if the account is active and has no pending issues | | Billing portal | Updates payment method and views invoices | To keep billing details up to date | | Available plans | Lists the account's billing options | To evaluate an upgrade or downgrade | | Top-up link | Generates a checkout to add credit | To keep a balance for consumption features, such as campaigns | What the payments area shows In Papo's payments area, you find a summary of your account status: the subscribed plan, the plan, available credit, and billing status. This view helps confirm whether the monthly fee has been processed and whether there is enough balance for modules that work on a consumption basis. In addition to the summary, the platform lists the available billing plans. This lets you compare limits and decide whether the operation needs more agents, more inboxes, or a smaller plan. The first Papo user is free and does not require a credit card; plan billing takes effect when new members are added to the team. How to access and use the billing portal The billing portal is the environment used to manage the subscription's financial details. Access is through the payments area of your account, with no separate registration required. In this portal you can: - update the registered payment method; - view previous invoices; - download documents for accounting control; - track the subscription's billing cycle. Because the link is generated within the Papo account itself, your data is protected and you do not need to send payment information to support agents. Change plan and limits without losing data If the operation grows, you can change plans through the payments area. The change adjusts agent, inbox, and module limits without deleting contacts, conversation history, or automations. Data remains linked to the account; only the plan capacity changes. The same applies to downgrades: if you want to reduce costs, you choose a plan with fewer features. Billing is recurring and the billing status appears in the subscription summary. Credits: separate payment for consumption The subscription covers access to the platform and the plan's features. Credits are a prepaid balance used for consumption features, such as bulk messaging campaigns in Disparador. To maintain the balance, the payments area generates a checkout link to top up credit. You choose the amount and complete the payment; the updated balance is visible in the account. This separation keeps the subscription cost predictable and lets you pay only for the volume consumed. Who this management is important for - Customer service teams that need to keep WhatsApp running without interruption. - Sales operations that use bulk messaging campaigns and need available credit. - Agencies and consultancies that adjust the plan according to the number of clients or agents. - White label resellers who, in addition to their own account, manage client subscriptions in the reseller panel. Frequently asked questions Where is the payment portal? Access is in the payments area of your Papo account. The platform generates the link to the billing portal, where you update billing details and view invoices. Can I change plans after creating the account? Yes. The payments area lists available plans and allows you to switch. Contacts, conversation history, and automations remain intact; only the limits and modules of the new plan change. Are subscription and credits the same thing? No. The subscription is the recurring charge for platform access and plan features. Credits are a separate balance consumed by features such as bulk messaging campaigns. How do I download previous invoices? In the billing portal, you view billing history and download invoices for financial control. The link to the portal is generated in the payments area of your account. What happens when adding a new team member? The first Papo user is free. When you add new members, plan billing takes effect, and the subscription summary displays the new status and amount. And in the white label reseller model? In the white label model, the approved reseller uses their own panel to track each client's subscription, plan, credit, and billing status, in addition to generating the billing portal link for the client. Read also - How to set up automatic billing and billing plans in the white label reseller model - How to manage your clients' WhatsApp credit consumption and avoid interruptions Start free and manage your subscription → The first Papo user is free; you only add billing when you invite new members to the team.

How to enable and customize desktop notifications in Papo

To enable and customize desktop notifications in Papo (https://papo.global/), you need to grant permission in your browser and adjust the alert preferences — sound and visual — directly in your profile settings inside the platform. You can also manage notification delivery separately for each inbox you handle. Keeping notifications tuned to your workflow is essential to ensure agility in customer service without overloading your attention. Papo offers controls so that each agent can personalize their experience, especially on an office computer, where multiple tabs and tasks compete for focus. The table below summarizes the types of desktop notifications and where to manage them: | Notification Type | Where it applies | How to Manage | Important Details | | :--- | :--- | :--- | :--- | | Browser Notifications | Desktop (Chrome, Firefox, Edge, etc.) | In your Papo profile settings and in your browser permissions. | Requires initial authorization. Displays a pop-up on your computer screen. | | Sound Alerts | Desktop (web version) | In your Papo profile settings. | Can be turned on or off independently of visual alerts. | | Notifications per Inbox | Desktop (web version) | In the settings of each inbox in Papo. | Lets you mute specific inboxes while keeping others active. | How desktop notifications work (browser) When you use Papo in a browser on your computer, you have two main types of alerts that complement each other: visual ones (system pop-ups) and sound ones. Both are controllable and can be turned on or off at any time. Enabling browser notifications The first time you access the Papo platform, the browser usually displays a request to allow the site to send notifications. To receive visual alerts for new messages even when the Papo window is in the background, you need to click "Allow". If you blocked this request by accident or changed the setting later, you can revert the permission directly in your browser settings. The typical path is to open the site information menu — usually represented by a padlock or shield icon next to the address bar — and find the "Notifications" option. Change the permission to "Allow" or "Ask" for the Papo domain. Customizing alerts in your Papo profile Inside the platform, you'll find notification preferences in your personal profile area. This is where you define how alerts behave, regardless of your browser settings. You can control: - Turn notification sound on/off: Ideal for those who prefer only visual alerts and want to avoid sound interruptions while serving customers. - Notify only for unread conversations: You receive alerts only for the first message of a new conversation or of a conversation you haven't opened yet. This avoids repeated notifications for the same thread. - Notify for all messages: An alert is issued for every new message that arrives, even in conversations already open in another tab. Managing preferences per inbox An important feature for teams that handle multiple channels is the ability to refine notifications per inbox. In the settings of each inbox (such as WhatsApp, Instagram, Telegram or email), you can choose to mute alerts for a specific inbox while keeping others active. This is useful, for example, when an agent is focused on closing sales via WhatsApp and doesn't need to be interrupted by new messages arriving in the general support inbox, which is being handled by another colleague. Who benefits most from customizing notifications Detailed alert customization is particularly valuable for profiles that need to balance concentration and readiness: - Sales agents: They need agility to reply to hot leads, but can mute sound alerts during calls or meetings. - Support managers: They want to monitor inbox volume without taking part in every conversation, opting for alerts only for mentions or unassigned conversations. - White label resellers: When setting up the platform for their clients, it's important to guide end users on these options so the tool adapts to each company's operation, not the other way around. Frequently Asked Questions Why am I not receiving notifications on my computer? Check three things: 1) Whether you granted notification permission to the Papo site in your browser settings; 2) Whether notifications are enabled in your profile preferences on the platform; 3) Whether the operating system is in "Do Not Disturb" or "Focus" mode, which can completely suppress visual alerts. Is it possible to receive notifications only for conversations assigned to me? Yes. In the notification settings, you can choose to receive alerts only for conversations in your personal queue or that were directly assigned to you, reducing the noise from the team's general inbox. How do I mute a specific inbox without turning off all notifications? Go to the settings of the inbox you want to mute (e.g., "Instagram Support") and turn off notifications for it. The other inboxes will continue to generate alerts as usual. Can I use sound and pop-up at the same time on desktop? Yes. Sound and visual notifications (browser pop-ups) are controlled independently. You can keep them both active so you don't miss any message, or turn one of them off as you prefer. Do notifications work if the Papo window is closed? No. Browser notifications (pop-ups) work with the browser open, even if the Papo window is in the background or minimized. If you close the browser completely, desktop alerts are no longer displayed. For that, consider also using the Papo mobile app. What should I set up first for a new agent on my team? Guide the agent to take three actions: accept browser notifications, set their sound alert volume in the Papo profile, and check which inboxes need to be active for their role. This ensures they start serving customers without missing messages and without unnecessary distractions. Read also - How to receive alerts for new conversations on Telegram - How to manage your clients' subscriptions and charges in the white label resale Start now and build your notification hub → Create your free Papo account and have all your team's conversations in one place, without missing any important message.

How to Change the Papo Interface Language

To change the Papo (https://papo.global/) interface language, go to your account settings and select the desired language option among Portuguese, English, and Spanish. The change is applied immediately to all team members who access the same account, without affecting the language settings of AI assistants or customer conversations. The platform supports three display languages, allowing you and your team to work in the language you feel most comfortable with. The language is set when the account is created and can be adjusted at any time, ensuring flexibility for multilingual operations or distributed teams. | Available language | What changes in the interface | | :--- | :--- | | Portuguese | Menus, buttons, labels, notifications, and fixed platform texts appear in Portuguese. | | English | The entire interface is displayed in English, ideal for international teams or those who prefer the language. | | Spanish | The platform uses Spanish, useful for operations in Latin America or Spanish-speaking teams. | How language selection works The interface language is an account setting, not an individual user setting. This means that when you change the language, all agents and administrators who access the same account will see the platform in the new language. The choice does not affect conversation content, AI responses, or texts sent to customers — these elements are controlled separately through assistant prompts and configured messages. During account creation, the language is requested along with other company data, such as time zone and industry. Later, you can change this preference in the account settings without needing to recreate the registration or lose data. Step by step to change the language 1. Go to your account settings in the Papo dashboard. The option is available to users with administrator permission. 2. Find the section that contains the language preferences. This area brings together the company's general settings, such as name, time zone, and language. 3. Select the desired language from the list: Português, English, or Español. 4. Save the change. The interface will automatically reload in the new language, and all team members will see the platform with the new setting. If your account is a white label reseller, the default language can be set for all reseller customers, and each end customer can change it individually if they have administrator permission on their own account. Who this setting is useful for - Multilingual teams that prefer to standardize the interface in English but serve customers in Portuguese or Spanish. - International operations that use Papo in different countries and want each team to see the platform in their native language. - White label resellers that set the default language for customers according to the region or the contractor's preference. - Users who set up the initial configuration in one language and later want to change it without needing a new account. Frequently asked questions Does changing the interface language affect AI responses? No. The interface language is independent of AI assistant behavior. To configure Capitão or Super Chat to serve in different languages, you need to adjust the prompt and knowledge base, as described in the specific articles about multilingual training. Can I set different languages for each agent? No. The interface language is an account setting, so all users who access the same account see the same language. If your operation requires each agent to have a different language, you need to create separate accounts. Is Spanish available on all screens? Yes. The complete interface — menus, modules, reports, and settings — is translated into Spanish, as well as Portuguese and English. Does changing the language change the time zone or other regional settings? No. Language is an independent preference. Time zone, date format, and currency are configured separately in the account preferences. What happens if I change the language while the team is using the platform? The change is applied immediately to everyone. We recommend informing the team before making the switch to avoid momentary confusion. How do I set the default language for my white label reseller customers? In the reseller settings, you can set the default language that will be applied to all new accounts created. Administrator customers can change this preference later if they wish. Read also - How to customize your white label reseller login screen - How to manage your subscription, plan, and payments in Papo Start free now → With your first user free, you can explore all Papo modules and already set the interface language for your team.

How to use the Papo API to list conversations and send messages programmatically

With Papo (https://papo.global/), you can use the REST API to list conversations, send text messages, apply tags, and assign conversations to agents, automating customer service processes without accessing the interface. The API offers endpoints that mirror the functionalities of the Conversations module, allowing external systems to manage interactions programmatically. | API Action | What it does | Example use | | :--- | :--- | :--- | | List conversations | Returns the account's conversations, with filters by status, tag, or agent | Monitor active or closed conversations from an external CRM | | Send text message | Sends a text message to a contact (respecting WhatsApp's 24-hour window) | Notify a customer about an order update | | Apply tag | Creates a tag (if it doesn't exist) and applies it to the contact and the open conversation | Mark conversations as “Urgent” or “Post-sale” automatically | | Assign conversation | Assigns a contact's open conversations to a specific agent | Route leads to the salesperson responsible for the region | How the Papo Conversations API works The Papo API follows the REST standard, with authentication via secret key (Bearer token) and JSON responses. All operations described here use the same authentication base and can be combined to create automated workflows — for example, a triage system that, upon receiving a new lead, lists recent conversations, applies a “New” tag, and assigns it to the on-duty agent. The API base is https://app.papo.global/api/v1. To use the conversations, tags, and assignment endpoints, you need an API token generated in the Papo panel. Complete documentation with specific endpoints and parameters is available at papo.global/pt/docs. Step-by-step to use the API resources 1. Generate an API token In the Papo panel, go to the developer or access tokens section. Create a secret key (sk_live_…) with the appropriate permissions to manage conversations. Store the token in a safe place — it will be sent in the Authorization header of all requests. 2. List conversations Use the conversation listing endpoint to get the account's conversations. The request accepts filter parameters such as: - Status: open, closed, or all conversations. - Tag: filters by one or more applied tags. - Agent: restricts to conversations assigned to a specific user. - Period: date range to limit the query. The response includes the conversation identifier, contact, channel, status, and last messages. With this data, you can monitor the volume of conversations or trigger conditional actions from an external system. 3. Send a text message To send a text message to a contact, use the message sending endpoint. The request requires: - Recipient number in international format (e.g., 5511999999999). - Message text. - Instance identifier (optional) — if your account has more than one WhatsApp connection, you can specify which one to use. The API returns a confirmation that the request was accepted. Remember that sending text messages is subject to WhatsApp's 24-hour window; for communications outside this period, you must use pre-approved message templates (HSM). 4. Apply tags to contacts and conversations The API allows you to manage tags in two ways: - Create a tag in the account: define a title, color, and description for the new tag. - Apply a tag: associate an existing tag with a contact and that contact's open conversation. If the tag doesn't exist yet, it will be created automatically during application. This is useful for automatically classifying conversations based on your system's rules — for example, marking as “Complaint” when the customer sends a specific keyword. 5. Assign conversations to agents With the assignment endpoint, you can assign an agent to all open conversations of a given contact. Just provide the contact identifier and the user/agent ID. The account's agent list can be obtained through the user listing endpoint, which returns the name, email, and ID of each team member. This functionality is essential for automatic routing: a CRM system can, upon identifying the lead's profile, assign it to the correct salesperson without manual intervention. Who should use the Conversations API - Operations that already use external systems (ERP, CRM, e-commerce platforms) and want to integrate Papo's customer service without duplicating efforts. - Support teams with complex routing rules, who need to classify and direct conversations automatically based on customer data. - Developers building custom dashboards or triggering notifications from customer service events. - White label resellers who manage multiple accounts and want to automate the configuration of tags and assignments for each client. Frequently asked questions Do I need an API token to use these endpoints? Yes. All requests to the Papo API require authentication via secret key, sent in the Authorization: Bearer sk_live_… header. Tokens are generated in the account panel. Does the API allow sending messages outside WhatsApp's 24-hour window? Sending text messages via the API respects the 24-hour window. For proactive communications outside this period, you must use approved message templates (HSM). Papo offers specific endpoints for sending HSM. Can I list conversations by tag? Yes. The conversation listing endpoint accepts a tag filter, allowing you to retrieve only conversations marked with one or more specific tags. How do I apply a tag to a contact via API? Use the tags endpoint, providing the tag identifier (or the data for creation) and the contact identifier. The tag will be applied to the contact and the corresponding open conversation. Does the API return the full conversation history? The conversation listing returns metadata and the last messages. To get the full message history of a specific conversation, consult the API documentation, which details the message retrieval endpoints. Is it possible to assign a conversation to an agent without knowing the user ID? You can first list the account's users (agents endpoint) to get the IDs and then use the assignment endpoint. The agent list includes name and email, making identification easier. Read also - How to use the Papo API to manage your white label reseller clients - How to use the Papo API to manage custom contact attributes Get started for free → Test the API and all Papo modules at no cost — the first user is free and does not require a credit card.

How to manage scheduled messages via API

With Papo's REST API (https://papo.global/), you automate the creation, listing, and cancellation of scheduled messages for WhatsApp and SMS, integrating communication scheduling directly into your systems, CRMs, or automation flows — without needing to access the dashboard manually. The Papo platform already offers a centralized area to manage scheduled messages, but when the volume of scheduled sends is high or when you need another software to trigger the sends, the API is the way. With it, you can create reminders, follow-ups, and notifications programmatically, keeping the same control you would have in the visual interface. Summary of scheduled message operations via API | Operation | What it does | When to use | | :--- | :--- | :--- | | Create schedule | Schedules a WhatsApp or SMS message to a contact on a specific date and time. | Schedule appointment reminders, sales follow-ups, or billing notifications from an external system. | | List schedules | Returns all scheduled messages, with the ability to filter by status (pending, sent, canceled, failed). | Sync the send schedule with a dashboard, check pending items before creating new schedules, or audit scheduled communications. | | Cancel schedule | Cancels a scheduled send before the trigger time. | Stop a message that is no longer relevant, such as a reminder for a canceled event or a follow-up that no longer makes sense. | How the integration works The Papo API follows the REST standard and uses Bearer token authentication. All write operations (creation and cancellation) require your account's secret key, generated in the dashboard's developer area. The base URL is https://app.papo.global/api/v1. To use the scheduled message features: 1. Generate a secret key in the Papo dashboard (developer/API area). Store it in a safe place — it is shown only once. 2. In each request, include the header Authorization: Bearer {your_secret_key}. 3. Use the specific endpoints for scheduled messages, according to the official documentation at https://papo.global/pt/docs. There you will find the exact paths, required parameters (such as contact ID, channel, content, date/time), and JSON payload examples. 4. To list schedules, you can apply filters by status, allowing you to query only pending or already completed sends. The API reflects the behavior of the platform's Scheduled Messages module: schedules created via API appear in the dashboard listing, and any cancellation made via API updates the status immediately. Who this automation is for - Developers and IT teams who need to integrate message scheduling into their own systems, such as ERPs, CRMs, or appointment scheduling platforms. - White label resellers who want to offer their clients the ability to schedule sends via API, increasing the value of the solution. - Operations with a high volume of follow-ups (sales, billing, attendance confirmation) that want to automate the creation of reminders without manual intervention. - Companies that use automation flows and trigger the creation of schedules from events in other tools. Frequently asked questions Do I need to have the Scheduled Messages module active to use the API? Yes. The API operates on the same functionality you find in the dashboard. If the module is available in your plan, the corresponding endpoints will also be accessible. Does the API allow scheduling messages with attachments or media? The official documentation details the supported content types. Currently, scheduling via the platform is focused on text messages. Consult the API reference to check whether media support is available at the time of your integration. How do I authenticate requests? Use your Papo account's secret key as a Bearer token in the Authorization header. The key is generated in the dashboard's developer area. Can I schedule messages for multiple contacts at once? The API allows creating one schedule per request. For multiple contacts, you can make sequential calls. Check the documentation to see if batch endpoints exist for your use case. What happens if I try to cancel a message that has already been sent? The API will return an error, because only schedules with pending status can be canceled. After the send is triggered, the message can no longer be changed. Where do I find the API keys? In the Papo dashboard, go to the developer area or API settings. The secret key is shown at the time of creation; if lost, you will need to generate a new one. Read also - How to manage scheduled messages in Papo: edit, cancel, and view - How to use the Papo API to list conversations and send programmatic messages Start automating your scheduled messages now → With Papo, you integrate WhatsApp, CRM, and AI in one place, at no initial cost.

How to archive conversations and contacts in bulk via API

To archive conversations and contacts in bulk programmatically, use the Papo REST API. With the contact update and conversation tag application endpoints, you can mark records as archived, keeping your database always clean without manual intervention — ideal for high-volume data operations or white label resellers managing multiple clients. Papo does not require a dedicated “archive” endpoint. Instead, you use the operations already available in the API to change the state of records: update a contact (by adding an archive tag or a custom attribute) and apply a tag to a conversation. This way, scripts or automations can process thousands of items in batch and organize the database according to your business rules. Summary of the bulk archiving process via API | Step | Action | Important detail | | :--- | :--- | :--- | | 1. Obtain the keys | Generate the secret key (sk_live_…) and copy the public key (pk_live_…) in the Papo dashboard. | The secret key appears only once; store it in a safe place. | | 2. Identify what to archive | List contacts or conversations that should be archived (by date, status, lack of interaction, etc.). | Use the listing endpoints with filters or export a CSV to feed the script. | | 3. Archive contacts | For each contact, send an update request including the “archived” tag or a custom attribute. | The contact update endpoint accepts the fields you want to modify. | | 4. Archive conversations | For each conversation, apply a tag such as “archived” using the tag endpoint. | The tag is automatically created in the account if it does not exist. | | 5. Verify the result | Check if the records appear with the archive marking and if the platform filters reflect the new organization. | Adjust the filters in the Contacts or Conversations module to hide archived items. | How it works – step by step 1. Authentication and keys Every call that modifies data requires the account's secret key. It must be sent as a Bearer token in the Authorization header (or in the X-Papo-Secret-Key header). The public key (fixed per account) can accompany the request in the X-Papo-Public-Key header — its use is optional, but if sent it must correspond to the same account as the secret key. Generate the keys in the Papo dashboard, in the developer area. The API base URL is https://app.papo.global/api/v1. Consult the official documentation to see the exact endpoints, parameters, and payload examples. 2. Identifying the records to archive Before triggering the updates, you need to know which contacts or conversations should be archived. The API offers listing endpoints that return the necessary data. For example, you can: - List contacts (search by name, email, phone, or date filters) to select those without interaction for X days. - List conversations and cross-reference with criteria such as status or last message date. With the list in hand, a script in Python, Node.js, or an automation in n8n can iterate through each record and execute the archiving action. 3. Archiving contacts in bulk The Papo API allows you to update an existing contact. To archive it, you can: - Add a tag (e.g., “archived”) to the contact. The update endpoint accepts the inclusion of tags. - Or update a custom attribute (if you have created a field such as “status” or “archived”) with the desired value. The important thing is that, after the update, the contact carries a marking that differentiates it from active ones. Since the API processes one contact per request, the bulk operation is done by executing multiple calls in sequence. Code examples in JavaScript and Python are available in the API documentation and can be adapted for the update endpoint. 4. Archiving conversations in bulk For conversations, the API offers an endpoint that creates a tag in the account (if it does not exist) and applies it to the contact and the open conversation. Thus, you can create the “archived” tag and apply it to all conversations you want to remove from the main view. The flow is similar to that of contacts: list the conversations, filter those that should be archived, and for each one, send the tag application request. The tag will be automatically created on the first call, if it does not already exist. 5. Checking the archiving After the script finishes, access the Contacts and Conversations modules in the Papo dashboard. Use the tag filters to view only the items marked as “archived” — or, conversely, to hide them and keep focus on active records. If the operation does not have the expected effect, review the payloads and authentication headers. Who this automation is for - Operations with a large volume of contacts that need to clean the database periodically, removing cold leads or closed conversations from the main view. - White label resellers managing dozens of client accounts and wishing to offer an automated organization service via API. - IT teams and developers building custom integrations to keep the CRM always lean, without relying on manual actions. - Companies that migrated data from other systems and now want to archive old records that will no longer be used daily. Frequently asked questions Does the Papo API have a specific endpoint for archiving? No dedicated endpoint is required. You use the contact update and conversation tag application endpoints to mark records as archived. The official documentation details the accepted parameters. Can I delete contacts or conversations instead of archiving? The current API does not offer deletion endpoints. The recommendation is to use archiving via tags or custom attributes, which keeps the data preserved but out of the main view. How do I authenticate requests? Include the Authorization: Bearer {your_secret_key} header in all write calls. The secret key is generated in the Papo dashboard, in the developer section. Is it possible to archive thousands of records at once? Yes. Just create a script that loops through the list of contacts or conversations and sends a request for each one. Tools like n8n can also orchestrate this process. Do archived conversations disappear from the inbox? They continue to exist, but by applying a tag such as “archived”, you can filter them out of the default view. The display depends on the filters configured in the Conversations module. Where do I find the API keys? In the Papo dashboard, access the developer area or API settings. The secret key is displayed only at the time of creation; if lost, you will need to generate a new one. Read also - How to use the Papo API to list conversations and send programmatic messages - How to use the Papo API to manage custom contact attributes Start for free and organize your database with the API → With Papo's free plan, you can already test the integration and archive contacts and conversations in bulk at no initial cost.

How to use the Papo API to manage Companies in the CRM

With the Papo REST API, you can list, search, create, update, and link contacts to CRM Companies — all through authenticated requests, without opening the panel. It's the programmatic way to keep B2B client management synchronized with external systems, ERPs, CRMs, or automation tools. Papo's API exposes resources from the Companies module so your operation can organize B2B accounts, consolidate linked contacts, and track recent conversations for each company. With secret key authentication and JSON responses, these endpoints allow you to integrate the account view into scripts, automations, and white label resellers. Summary of Companies operations via API | Operation | What it does | When to use | | :--- | :--- | :--- | | List companies | Returns the companies registered in the CRM with name, domain, and number of contacts. | Audit the account base or synchronize companies with another system. | | Search by name or domain | Locates specific companies in the CRM. | Find the B2B account before updating data or linking contacts. | | Get company details | Returns the data of a company by its identifier. | Consult a specific account during an integration. | | Create company | Creates a new company; name is required, while domain and description are optional. | Register B2B accounts automatically from an ERP, website, or external flow. | | Update company | Updates the name, domain, and description of an existing company. | Keep the CRM always aligned with the B2B client base. | | Link contact | Links an existing CRM contact to a company. | Consolidate the relationship and history between contacts and accounts. | | List contacts and conversations | Brings the contacts linked to the company and the recent conversations of those contacts. | Have a complete view of the account during service or follow-up. | How API authentication works All write routes, including Companies operations, require the account's secret key. It must be sent as a Bearer token. The account's public key is optional, but if sent, it must correspond to the same account as the secret key. The API base URL is https://app.papo.global/api/v1. Keys are generated in the developer area of the Papo panel. The secret key appears only once upon creation; store it in a safe place and revoke it if there is any suspicion of leakage. Since the API is REST and uses JSON, any language with HTTP support can be used to integrate Companies into scripts, ERPs, CRMs, or automation tools. The official documentation at https://papo.global/pt/docs provides details on authentication, parameters, responses, and code examples. How to manage Companies via API in practice 1. Access the developer area of the Papo panel and generate a secret key. Also copy the account's public key. 2. In each request, authenticate with the secret key as a Bearer token. If you want to reinforce validation, send the public key in the header indicated in the documentation. 3. To list the CRM companies, call the Companies listing endpoint. The response brings the name, domain, and number of contacts for each account. 4. To locate a specific company, use the search by name or domain endpoint. This way you get the identifier needed to update data or link contacts. 5. To create a company, send a JSON payload with the required name. Domain and description can be included as optional data. 6. To update a company, send the new values for name, domain, or description in the update endpoint. 7. To link an existing contact, use the contact identifier and the company identifier in the link operation. Since the API processes one operation per request, bulk management is done by executing calls in sequence. A script in Python, Node.js, or an automation in tools like n8n can read accounts from a CSV or ERP, register companies, link contacts, and collect responses for error handling. Who this integration makes sense for - B2B companies that keep accounts in another CRM or ERP and want to automatically synchronize with Papo's Companies module. - Sales teams that work with account clients, such as agencies, consultancies, SaaS, and providers, and need to consolidate contacts and conversations by company. - Operations that capture companies from forms, landing pages, or external systems and want to create them in the CRM without manual rework. - White label resellers and integrators who connect Papo to client systems and want to keep account management consistent across different environments. - IT teams that build custom integrations using the API as a bridge between the company base and the rest of the operation. Frequently asked questions Do I need to create the contact before linking it to a Company? Yes. The API links a contact that already exists in the CRM. To register a new contact, use the contact creation endpoints and then link it to the company. What data can I update in a Company via API? You can update the company's name, domain, and description. Creation requires the name; domain and description are optional. Does the API allow listing a Company's conversations? Yes. The Companies module allows listing the contacts linked to a company and the recent conversations of those contacts, facilitating the account view during service. Is the authentication the same as used in other Papo endpoints? Yes. Write routes require the account's secret key, sent as a Bearer token. The public key is optional and, if sent, must correspond to the same account. Where can I find the exact paths and payload format? In the official API documentation, available at https://papo.global/pt/docs. There you will find details on authentication, parameters, responses, and code examples for Companies and other resources. Can I use the API to synchronize the Companies base with my current CRM? Yes. Since the API is REST and uses JSON, you can automate listing, creation, updating, and linking of contacts in sequence, keeping both systems aligned. Read also - How to use the Companies module in Papo's CRM - How to use the Papo API to manage custom contact attributes Start for free and manage Companies in the CRM via API → The first Papo user is free forever, no credit card required.

How to integrate Papo with Zapier using API and webhooks

To integrate Papo (https://papo.global/) with Zapier, you use Papo's REST API to execute actions and native webhooks or Flows to send events from Papo to Zapier. This way, an event such as a new conversation or a won deal in Kanban can automatically trigger actions in hundreds of applications connected to Zapier. Papo does not rely on an exclusive connector to work with Zapier: the platform exposes REST endpoints and allows you to create webhooks, which are exactly the mechanisms Zapier uses to receive and send data. This guide shows the connection in two directions: Papo events as triggers in Zapier and calls to the Papo API as actions. Integration summary | Resource | What it does | Where to configure | | :--- | :--- | :--- | | Papo REST API | Authenticated by secret key; allows listing account, instances, contacts, sending messages, and using AI | https://app.papo.global/api/v1 with key generated in the panel at https://app.papo.global/developers | | Native webhook | Sends account events to a configured URL | Automations module | | Kanban webhook | Sends sales funnel events to a configured URL | Kanban module | | Flows | Creates visual automations; a trigger such as new conversation can call a webhook action | Flows module | | Webhooks by Zapier | Receives Papo's webhook and triggers actions in hundreds of apps | Zapier | What you need before you start - A Papo account with access to the panel. - A Zapier account. - The Papo API secret key, created at https://app.papo.global/developers. - A Zapier webhook URL to receive events. The secret key follows the format sk_live_... and is displayed only once at creation. Store it in a safe place, because it authenticates API calls. How the integration works in two directions From Papo to Zapier (trigger) 1. In Zapier, create a Zap and choose Webhooks by Zapier as the trigger, in the Catch Hook option. Zapier generates a unique URL. 2. In Papo, create a native webhook, a Kanban webhook, or a Flow with a webhook action. 3. Paste the Zapier URL into the destination field of the webhook or action. 4. Configure the event that should trigger the send. For new conversations, use a Flow with the New conversation trigger. For funnel events, use Kanban webhooks. 5. In Zapier, add the desired action: send email, create a row in a spreadsheet, register a lead in another CRM, notify a Slack channel, etc. From Zapier to Papo (action) 1. In Zapier, use Webhooks by Zapier as an action, usually with a custom request. 2. Point to the base https://app.papo.global/api/v1. 3. Include the header Authorization: Bearer sk_live_... or X-Papo-Secret-Key and, if desired, X-Papo-Public-Key. 4. Choose the endpoint according to the action: POST /api/v1/messages to send a WhatsApp message, GET /api/v1/contacts to list contacts from Extractor, GET /api/v1/instances to check WhatsApp connections, among others. 5. Map the data coming from previous steps of the Zap to the request body. Practical automation examples - New WhatsApp conversation generates a lead in another system: a Flow triggers a webhook to Zapier whenever a new conversation arrives in an inbox. Zapier formats the data and creates the lead in the company's CRM. - Won deal in Kanban updates a spreadsheet: the Kanban webhook sends the event to Zapier, which records the won card in a spreadsheet or financial system. - Programmatic messages: Zapier calls POST /api/v1/messages to send a reminder to the customer after they fill out a form in another app. - AI responses: Zapier can call POST /api/ai/v1/complete to generate a response with the Papo account prompt and use the result in another flow. Who this integration is useful for - Sales teams that need to sync won deals with spreadsheets, CRMs, or billing tools. - Support teams that use multiple channels and want to log conversations in help desk systems. - Marketing operations that trigger campaigns from CRM events, such as a new extracted contact. - Companies with a diverse stack that want to reduce manual work between WhatsApp, CRM, email, and spreadsheets. Frequently asked questions Do I need an official Papo connector in Zapier? No, it is not necessary. The integration uses Papo's REST API and webhooks, which work with the Webhooks by Zapier app. Details of available endpoints are in the API documentation. Which Papo events can start a Zap? You can use Flows for events such as new conversation and native or Kanban webhooks for automation and sales funnel events. The complete list of available webhooks appears in the Papo panel. How do I authenticate the Papo API in Zapier? Use the secret key in the Authorization: Bearer sk_live_... header or in the X-Papo-Secret-Key header. The public key (pk_live_...) is optional when sent together with the secret key. Can I send WhatsApp messages through Zapier? Yes. You can make a request to POST /api/v1/messages providing the destination number and the text. The message is sent through the WhatsApp connected to your Papo account. Can Zapier update Kanban cards? Yes, via API. Papo allows you to list cards, create a card in a stage, move cards, and mark them as won or lost, which can be triggered by Zapier. What should I do if the webhook does not reach Zapier? Confirm that the webhook or Flow is active, that the Zapier URL was pasted correctly, and that the key used in the calls is valid. Flow execution logs help identify the error. Read also - Automations in Papo: Rules, Macros, Flows, and Webhooks – which one to use? - How to use the Papo API to list conversations and send programmatic messages Start for free and connect your channels → Create your free Papo account to centralize service, CRM, and automations in a single panel.

How to view and manage Wavoip tokens in Papo

To manage the Wavoip tokens used in voice inboxes on Papo, you can view the list of masked tokens per inbox and, when necessary, revoke or generate a new token by accessing the settings of the inbox itself. This management ensures the connection to the telephony system remains secure and under control, without needing to open another dashboard. Papo stores the Wavoip API token in encrypted form and displays it, in the voice inbox settings, always masked. This keeps the credential protected while you perform auditing and maintenance operations. | Action | Description | When to use | | :--- | :--- | :--- | | View token | Temporarily reveals the full token (only to the logged-in administrator). | To copy the token and validate the connection or prepare a migration. | | Revoke token | Immediately blocks access using the current token. The voice inbox will be inoperable until a new token is entered. | If there is suspected leakage, deactivation of an employee, or scheduled credential rotation. | | Generate new token | Replaces the current token with a new one generated by the system itself. After generation, the new value is displayed only once so you can copy it and update the inbox configuration. | Periodic credential rotation, due to security policy, or when the old token is accidentally revoked. | How to manage Wavoip tokens in Papo Managing tokens is done directly in the settings of the inbox associated with the voice channel with the Wavoip provider. Access is restricted to users with administrative permissions on the account. 1. Go to Settings in the Papo dashboard. 2. Go to the Inboxes section and find the Voice inbox that uses the Wavoip provider. 3. Click the inbox name to open settings or, if available, the corresponding edit icon. 4. On the inbox details screen, scroll to the credentials block. You will find the Wavoip token field, displayed in masked format (e.g., ••••••••••1234). 5. To view the full token, click Show token. The actual value will be shown on screen while you are on the page; upon reloading or leaving, it will be masked again. 6. To revoke the current token, click Revoke token. From that moment on, the Wavoip integration will be interrupted until a new token is provided. Use this action with caution. 7. To generate a new token, click Generate new token. The old token will be permanently invalidated and a new value will be generated. Copy the token immediately and, if necessary, enter it again in the inbox configuration field (if generation does not fill it automatically). After generating a new token, Papo automatically uses this new credential in API calls to the Wavoip system. No additional action in the Wavoip dashboard is necessary; just ensure the token stored in Papo is the same as the one you initially configured with the provider. Who needs this management - IT administrators and operations leaders who need to audit who has access to integrated telephony. - Companies with security policies that require periodic credential rotation. - Teams that deactivate voice channels for periods and want to cut the link without deleting the inbox. - White label resellers who manage multiple accounts and need to apply security best practices to each one. FAQ What happens if I revoke a token? Revoking a token immediately interrupts the voice inbox connection with Wavoip. Agents will no longer be able to make or receive calls on that inbox until a new valid token is entered. The inbox settings and call history are not affected. Can I have more than one token per inbox? No. Each Voice inbox with Wavoip uses a single token. If you need multiple telephony connections, create separate inboxes, each with its own token. Is the token visible to any user on the account? No. The token is displayed only in masked form in the interface. Only users with administrative permissions can click “Show token” to reveal the full value, and this action is logged for auditing purposes on the platform. Do I need a Wavoip account to generate the token? Yes. The token you manage in Papo is the credential that your Wavoip dashboard provides for integration. To get a new token, access your Wavoip dashboard, create an API key, and paste it into the Papo inbox settings. If I generate a new token in Papo, do I need to update anything in Wavoip? No. The token generated in Papo only replaces the value stored locally. Since the Wavoip provider expects any valid token you created earlier, just ensure that the token entered in Papo matches an active token in your Wavoip account. If you revoked the token in Wavoip, you will need to generate a new one there and paste it into Papo. Is it safe to manage tokens directly in the browser? Yes. Communication between your browser and Papo is done via HTTPS, and the token value is transmitted only at the moment of display or replacement. Papo does not store the token in plain text in the database; it is encrypted. Start free and centralize voice, WhatsApp, and CRM in one place → With Papo you integrate your Wavoip telephony and manage everything alongside text channels — without spreading credentials.

How to add a new agent to your team in Papo

In Papo Global (https://papo.global/), you add a new agent to your team from Settings > Agents. An administrator enters the employee’s name, role, and email address; the invitee receives a link to create a password and can access the platform immediately. The same screen lets you edit details, reset passwords, adjust availability, and remove agents, keeping operation control centralized. Process summary | Step | What to do | Detail | | :--- | :--- | :--- | | 1. Access settings | Click the gear icon and go to Agents | The menu only appears for users with the Administrator role. | | 2. Start registration | Click the Add Agent button | The form will be displayed. | | 3. Fill in the details | Enter Agent Name, Role, and Email Address | The role defines what the person can see and do in the account. | | 4. Finish | Click Add agent | The agent will receive an invitation email. Until they accept, the status in the list will be Pending Verification; afterward, Verified. | How to add an agent – step by step 1. In the side menu, click Settings, then the Agents tab. 2. Click Add Agent (top right). 3. In Agent Name, enter the name that will appear to the team — for example, “Ana Maria”. 4. Under Role, choose one of the options: - Agent: handles conversations in the inboxes they have access to. Ideal for most of the team. - Administrator: full access, including settings, channels, agents, and billing. Use only for account leaders and managers. - Custom roles: appear here if your account has already created specific profiles. 5. In Email Address, enter the employee’s work email. 6. Click Add agent. The message “Agent added successfully” confirms the action. 7. The employee will receive an email invitation. Upon accepting, they will create a password and can log in. Until then, the list shows Pending Verification. 8. If the email already has a Papo Global account (for example, the person works at another company that uses the platform), they are added automatically, without a new invitation, and sign in with the password they already have. Manage existing agents In the agent list, each row displays icons for management actions. The main ones are: - Edit: opens the “Edit Agent” screen. You can change the Agent Name, Role, and Availability field (options: Online, Busy, or Offline). After editing, save by clicking Edit agent. Availability can also be changed by the agent themselves. - Reset password: within the edit screen, this option sends the agent an email with instructions to create a new password. You do not view or set the password. - Delete: removes the agent from the account. Conversations they handled are not deleted; only access is revoked. You must confirm deletion. Important restrictions: - You cannot edit or delete your own user from this screen. - The account’s last verified administrator cannot be deleted, ensuring the account never ends up without an administrator. Organize agents into teams and inboxes After adding agents, it’s time to organize who handles what. Administrators can create teams and add agents to them. Then they associate these teams with specific inboxes (WhatsApp, Instagram, Telegram, email, website chat, etc.). This way, each group sees only the conversations that are their responsibility, avoiding confusion and overlapping service. How much does each agent cost? On Papo’s Silver plan, the first user is free forever. Each additional user costs R$ 97/month. If the account reaches the contracted limit, a warning will appear when trying to add a new agent, and the registration will not be created. To learn more, see the pricing page on the website. Frequently asked questions I don’t see the “Agents” menu in Settings. Why? The screen is only available to users with the Administrator role. Ask an account administrator to add the new agent or change your role. I got “The email entered is already in use.” What should I do? This means that email is already registered in your account. Use the “Search agents…” search to find it in the list. Can I set the agent’s availability? Yes. The administrator can change availability in “Edit Agent,” choosing between Online, Busy, or Offline. The agent themselves can also change their availability from the dashboard. If I delete an agent, do their conversations disappear? No. The conversations remain in the account. The agent only loses access to the platform. The agent received the invitation but cannot create a password. What now? Ask the agent to check their spam or junk folder. Also confirm that the email address entered is correct. If the problem persists, an administrator can resend the invitation using the password reset option in the agent’s edit screen. Can I limit an agent to just one inbox? Yes. To do this, you need to create a custom role that restricts the visible modules and associate the agent exclusively with the team responsible for that inbox. See the article on limited access for the full step-by-step. Read also - How to create and manage custom user roles in Papo - How to use Internal Chat for group conversations in Papo Start free and build your team → The first user is free forever, and you add extra agents for R$ 97/month.

How to change the email address used to access your Papo account

To change the email address used to access your account on Papo (https://papo.global/), go to your profile settings inside the platform, edit the email field and confirm the change — the new address will then be used for login, password recovery and account notifications. Keeping your access email up to date is essential to make sure you receive important notices, such as due date reminders or new conversation alerts, and to recover access if you forget your password. The process is quick and can be done at any time, with no need to contact support. | Step | What to do | Where | | :--- | :--- | :--- | | 1. Log in | Sign in to Papo with your current email and password | chat.papo.global/app/login | | 2. Open settings | Go to the Settings menu in the bottom-left corner | Main dashboard | | 3. Go to Profile | Click Profile or My Account | Inside Settings | | 4. Edit email | Find the email field and enter the new address | Profile page | | 5. Confirm | Follow the verification (current password or a link sent to the new email) | As requested | | 6. Save | Save the change and use the new email on your next logins | Save button | How to change your access email step by step 1. Log in to your Papo account Access the platform with the email and password you currently use. If you don't remember your password, you'll need to reset it before continuing (see the article about password recovery in the Read also section). 2. Go to Settings In the bottom-left corner of the dashboard, click the Settings icon or menu. This is where you manage account preferences, team and integrations. 3. Open your Profile Inside settings, select the Profile option (or My Account, depending on the interface version). This screen shows your personal data, such as name, photo and login email. 4. Edit the email field In the field for the email address, delete the current value and type the new email you want to link to your account. Make sure the address is correct and active, since it will be used for all platform communications. 5. Confirm the change For security reasons, Papo may ask for an additional confirmation. This can happen in two ways: - Entering your current password to authorize the change. - Receiving a verification link at the new email address — in that case, open your inbox (and your spam folder) and click the link to validate the change. 6. Save your changes After confirming, click Save. From that moment on, the new email will be your login identifier. Use it whenever you access Papo and to recover your password, if needed. Who this change is useful for - Users who have changed email addresses and need to keep their access linked to a current address. - Professionals who want to centralize Papo notifications in a specific corporate or personal email. - Teams reviewing permissions that want to ensure every agent uses a verified email under the company's control. - Anyone who has lost access to the old email but can still log in (otherwise, you'll need to contact support). Frequently asked questions Can I change my email if I don't remember my current password? Not directly. To change your email, you need to be logged in. If you've forgotten your password, use the "Forgot my password" option on the login screen to reset it and then follow the steps above. If you've also lost access to the old email, contact Papo support to verify your identity. Do I need to confirm the new email? Yes. The platform may require you to click a link sent to the new address or enter your current password. This extra verification protects your account against unauthorized changes. What happens to the notifications I was already receiving? Papo notifications (such as due date reminders or new conversation alerts, when configured) are automatically sent to the new email. No rule or flow is lost — only the destination is updated. Can I use the same email on two different accounts? Each Papo account requires a unique email address. If you try to register an email that is already in use, the platform will tell you that the user already exists. To manage multiple accounts, use different addresses. How long does it take for the change to take effect? The change is immediate after saving and confirming. You can already use the new email on your next login. Notifications also start using the new address right away. Read also - How to recover your Papo password Start for free → Create your Papo account with no commitment and get access to all modules so you can test the platform hands-on.

How to use the Papo API to create a signup form and populate the CRM automatically

With the Papo REST API, you can build an endpoint on your website that receives the data from your signup form and calls the contacts API to create records in the CRM automatically, including custom attributes — eliminating manual data entry and speeding up lead onboarding. Instead of exporting spreadsheets or copying data between systems, this integration turns every new signup on your website into a contact in the Papo CRM in real time. The flow is simple: the form sends the data to a backend you control, that backend authenticates with the Papo API and creates the contact with name, email, phone and any custom fields your operation needs. Integration summary | Component | What it does | Example | | :--- | :--- | :--- | | Website form | Collects the lead's name, email, phone and extra fields. | Capture page, landing page, checkout. | | Intermediate endpoint | Receives the form data and calls the Papo API. | Script in Node.js, Python or automation in n8n/Zapier. | | Papo contacts API | Creates the contact in the CRM with the submitted data. | Authenticated POST request with a secret key. | | Custom attributes | Adds fields such as source, interest or score to the contact. | custom_attributes with "origem": "site", "plano_interesse": "gold". | How it works: step by step 1. Generate the API keys in the Papo dashboard Go to the developer area of your Papo account and create a secret key. The account's public key is also visible on that screen. The secret key is shown only once; store it in a safe place and never expose it on the frontend. 2. Create the form on your website Build the form with the fields you want to send to the CRM: name, email, phone and any additional data (interest, source, city, etc.). The form must make an HTTP request (POST) to the endpoint you will build in the next step. 3. Build the intermediate endpoint On your server or in a serverless function (Node.js, Python, PHP, etc.), create a route that receives the form data. This code will be responsible for: - Validating the received fields. - Building the JSON payload for the Papo API. - Authenticating with the secret key (Bearer token) and, optionally, sending the public key in the X-Papo-Public-Key header. - Calling the Papo contact creation endpoint. 4. Call the Papo contacts API Use the contact creation endpoint (see the official documentation at https://papo.global/pt/docs for the exact path and payload format). Send at least a name and email or phone. The API response will confirm the creation with the new contact's data. 5. Add custom attributes If your account has custom attribute definitions (such as "source", "utm_source", "score"), you can send them in the same payload or in a complementary call. The API allows you to set/merge custom_attributes on the contact, eliminating the need to fill in these fields manually later. 6. Handle the response and return to the user After successful creation, your endpoint can redirect the lead to a thank-you page or display a success message. In case of an error (invalid key, missing data), log it and return a friendly message. Since the Papo API is REST and uses JSON, any language with HTTP support can be used. The official documentation provides examples in JavaScript, Python and curl, as well as details on authentication and error codes. Who this integration makes sense for - Websites and landing pages that capture leads and want to eliminate manual data transfer to the CRM. - E-commerces and SaaS that want to automatically create a contact at the moment of signup or purchase. - Agencies and consultancies running lead generation campaigns that need leads to enter the CRM in real time for immediate follow-up. - White label resellers and integrators who build custom flows for clients, connecting website forms to Papo without manual intervention. - Marketing and sales teams that use custom attributes for segmentation and want those fields filled in automatically at the source. Frequently asked questions Do I need advanced programming knowledge to implement this integration? Yes. You need to develop an endpoint on your server or use automation tools (n8n, Zapier) to bridge the form and the Papo API. The code itself is simple, but it requires basic knowledge of HTTP and JSON handling. Can I use any programming language? Yes. The Papo API is REST and responds in JSON. Any language with HTTP request support (Python, Node.js, PHP, Ruby, etc.) can be used. The official documentation provides examples in JavaScript and Python. Is it possible to create custom attributes directly when creating the contact? Yes. The Papo API allows you to set the contact's custom_attributes at creation time or update them later. See the documentation for the exact payload format and to check whether the attribute definitions already exist in the account. How do I keep the secret key secure? The secret key must never be exposed on the frontend (public HTML/JavaScript). It should only live on the server, in environment variables. Use HTTPS for all communications and revoke the key immediately if there is any suspicion of a leak. What should I do if the API returns an error? The Papo API returns standardized responses with success: false and an error object containing the code and message. Handle these errors in your code: validate that the required fields were sent, check that the key is active and that the payload format is correct. The documentation lists the main error codes. Can I use this integration with forms from platforms like WordPress, Typeform or RD Station? Yes. You can set up webhooks on these platforms to send the form data to your intermediate endpoint, which will then call the Papo API. Another alternative is to use ready-made integrations via Zapier or n8n, creating a flow that receives the form event and triggers contact creation in Papo. Read also - How to use the Papo API to manage Companies in the CRM - How to integrate Papo with Zapier using API and webhooks Start for free → Create your free Papo account and start integrating signup forms with the CRM in minutes, with no manual data entry.

How to integrate Papo with Slack to receive notifications of new conversations

To receive a notification in Slack every time a customer starts a conversation in a specific inbox in Papo (https://papo.global/), you must set up a Flow that triggers a Webhook to the desired channel. This keeps your support or sales team alert in real time, without having to constantly monitor the platform. The integration uses Slack's Incoming Webhooks and Papo's Flows, turning a new conversation into an automatic alert with no complex code. You choose the inbox, customize the message content, and ensure no one misses an important lead or ticket. | Step | Action | Tool | | :--- | :--- | :--- | | 1. Get the Webhook URL in Slack | Create an App, enable Incoming Webhooks, and copy the sending URL | api.slack.com | | 2. Create the Flow in Papo | Set up a new flow with the “New conversation” trigger and the “Webhook” action | Flows module (Papo) | | 3. Test the notification | Start a conversation in the chosen inbox and check that the message arrives in the Slack channel | Papo + Slack | How it works — step by step 1. Get the Webhook URL in Slack First, go to the Slack API (api.slack.com), create an App (or use an existing one), enable Incoming Webhooks, and generate a unique URL for the channel where the alerts will be posted. Note this URL — it will be used in the Flow configuration. 2. Create a new Flow in Papo In the Papo dashboard, go to the Flows module and click to create a new flow. Give it a name that identifies the notification, such as “New conversation alert in Slack”. 3. Configure the trigger Add a Trigger node and define that the flow should start when a New conversation arrives. Choose the specific inbox (e.g., WhatsApp number, Instagram, or another connected channel) that should generate the alert. This way, you notify only the channels that really matter. 4. Add the Webhook action After the trigger, insert an Action node and select the Send Webhook option. In the configuration field: - URL: paste the Slack Webhook URL. - Method: keep POST. - Payload: define the content that will be sent. Use dynamic conversation variables to customize the alert, such as {{contact.name}}, {{message.text}}, and {{inbox.name}}. Example in JSON: { "text": "New conversation from {{contact.name}} in the {{inbox.name}} inbox: {{message.text}}" } Adjust headers only if necessary; the default usually works. 5. Activate the Flow and test Save and activate the flow. To test, send a message to the configured inbox — for example, message your own WhatsApp number connected to Papo. Within a few seconds, the notification should appear in the Slack channel. If it does not arrive, check whether the flow is active, whether the Webhook URL is correct, and review the execution log inside the Flows module. Who this integration is useful for - Support teams that use Slack as their communication hub and need immediate alerts about new tickets. - Sales teams that monitor incoming leads in specific channels, such as a campaign WhatsApp inbox. - Operations with multiple inboxes that want to consolidate notifications in one place, without switching between tabs. - Managers who want to track the volume of new conversations without constantly opening the Papo dashboard. Frequently asked questions Do I need to have a Webhook configured in Slack before using the Flow? Yes. You need to create an App in Slack, enable Incoming Webhooks, and copy the generated URL. This procedure is done outside Papo, in the Slack developer interface. Can I send the exact content of the customer's message in the alert? Absolutely. In the Webhook action payload, you can include variables such as the conversation text, contact name, and channel, building a rich, contextual notification. What happens if the request to Slack fails? The Flow will log the error. You can add handling actions, such as sending a backup email or creating an internal task, to ensure the team does not miss the critical alert. Is it possible to send notifications to different Slack channels depending on the inbox? Yes. Simply create a separate Flow for each inbox and point it to the Webhook URL of the desired Slack channel. Consequently, support conversations go to one channel and sales leads to another, for example. How do I test without disturbing the team? After activating the flow, use a test contact (such as your own personal number) and send a message to the configured inbox. Confirm that the notification appears only in the designated channel. You can delete the test flow after validating. Is there an additional cost to use Webhooks in Papo? Flows and Webhook sending features are included in Papo plans. Detailed information about limits and subscriptions is available on the website. Read also - How to export conversation data to Google Sheets via webhook - How to create a Flow to send automatic birthday messages via WhatsApp Start for free → Try Papo for free and start automating your team's notifications today.

How to get started with the Papo API: authentication and first call

To start using the Papo Global API (https://papo.global/), you need to generate a secret key in the dashboard, authenticate requests with the Authorization header, and make REST calls to the base https://app.papo.global/api/v1. The first practical test is to list Extrator contacts with a simple cURL command. The Papo API is REST, uses JSON, and accepts requests from any origin (CORS enabled). With it, you connect CRMs, automation platforms (such as n8n), ERPs, or your own backend to Papo’s support, sales, and AI ecosystem. Summary of essential elements | Element | Description | |---|---| | Public key (pk_live_…) | Fixed identifier of your account, can be exposed on the front end | | Secret key (sk_live_…) | Authentication token, must be kept secret and used only on the server | | Authentication | Header Authorization: Bearer sk_live_... (or X-Papo-Secret-Key) on all calls except GET /api/v1 | | Base URL | https://app.papo.global/api/v1 | | Example endpoint | GET /api/v1/contacts — lists extracted contacts (Extrator), with pagination | Step by step for the first call 1. Create your API keys Go to the developers page in the Papo dashboard (available at app.papo.global/developers). There you can generate a named secret key — for example, “first-test” — and copy it immediately. The key is shown only once; after that you can only revoke it and create another. The public key (pk_live_…) is fixed per account and is visible on that same page at any time. Although optional in requests, if you send it, it must be associated with the same account as the secret key. 2. Choose the endpoint For this guide, we will use GET /api/v1/contacts, which lists leads extracted by the Extrator module. You can paginate the results with the page (default 1) and per_page (1 to 100, default 20) parameters. A text query with q is also accepted to search by company, phone, or email. 3. Make the call with cURL With the secret key in hand, build the request. The following example lists up to 20 contacts: curl "https://app.papo.global/api/v1/contacts?page=1&per_page=20" \ -H "Authorization: Bearer sk_live_…" Replace sk_live_… with your secret key. If you want to use the alternative header, do: curl "https://app.papo.global/api/v1/contacts" \ -H "X-Papo-Secret-Key: sk_live_…" The response is a JSON with success: true and the data inside the data object. If there is an error, the JSON will contain success: false and an error object with an explanatory code and message. From here, you can explore other endpoints documented on the API page, such as sending messages (POST /api/v1/messages), account details (GET /api/v1/me), or completing texts with AI (POST /api/ai/v1/complete). Who this guide is for This content is aimed at developers who want to integrate Papo with external systems — CRMs, automation tools (n8n, for example), or their own applications. If you are an end user who just wants to connect channels and provide support, the Help Center offers other, more suitable articles. FAQ Do I need to send the public key on every call? No. The public key is optional. If you choose to send it, it must match the account of the secret key used. Does the secret key expire? It does not expire automatically. You can revoke it at any time from the dashboard and create a new one if you suspect a leak. Can I test the API with a free account? Yes. The first Papo user is free, and you can generate keys to explore the API. Access to modules such as Extrator may consume balance depending on usage, but key creation and basic read calls can be tested at no additional cost. What should I do if I lose the secret key? Create a new named key in the developers dashboard. The previous key cannot be recovered; it can only be revoked for security. Can I use the API to send bulk messages? Yes, the POST /api/v1/messages endpoint allows you to send text messages. However, respect the platform’s consent policies and terms of use. Does the API list only Extrator contacts? The GET /api/v1/contacts endpoint returns extracted contacts. To manage the unified CRM base (search, create, and update any contact), you can consult the complete API documentation. Read also: How to use the Papo API to create a signup form and automatically populate the CRM · How to use the Papo API to monitor credit consumption and white label reseller invoices Start free on Papo Global → First user R$ 0, no card. Learn more at papo.global.

How to restrict an agent's access to contacts of a specific company

To restrict an agent's access to contacts of a specific company in Papo (https://papo.global/), you need to create a custom role that allows access to the Contacts and Companies modules, associate the agent with a dedicated team, and configure the company so that only that team can view its contacts in the CRM. This configuration is ideal when you need an external agent, a partner, or an outsourced team to access only the data of a corporate client, without seeing contacts from other companies in the database. Configuration summary | Step | What to do | | :--- | :--- | | Custom role | Create a profile that grants access to the Contacts and Companies modules, blocking modules such as Reports, Settings, or Kanban. | | Dedicated team | Create a team that will contain only the agents who should view the company. | | Company association | In the Companies module, edit the desired company and restrict access to only the created team. | | Agent invitation | Invite the agent with the custom role and include them in the dedicated team. | | (Optional) Inbox | Link the team to the company's inbox to also limit visible conversations. | How company restriction works in the CRM Papo organizes access to contacts through teams, roles, and the Companies module. To limit an agent to only see contacts linked to a specific company, you combine these three features: 1. Custom role – defines which modules the agent can access (e.g., Contacts and Companies, without access to Reports or Settings). 2. Dedicated team – the agent is placed in a team that will have exclusive access to the company in the CRM. 3. Restriction in the Companies module – when editing the company, you indicate which teams can view it. Only members of those teams will see the company and, consequently, the contacts linked to it. Thus, even if there are other companies and contacts in the account, the agent will only see the company for which they are authorized and the contacts associated with it. Step by step 1. Create a custom role with access to the necessary modules The custom role controls which platform modules the agent can see. For minimal access focused on contacts of one company: - Go to Settings in the side menu. - Scroll to Custom Roles and click Add custom role. - Give it a name (e.g., "Agent Company X"). - In permissions, check only the Contacts and Companies modules. Leave modules such as Reports, Settings, Kanban, or Conversations unchecked, as needed. - Save the role. Important: The custom role controls module visibility, but it does not restrict which companies or contacts appear within them. The company restriction is done in step 3. 2. Create a dedicated team for the company - Still in Settings, go to the Teams (or Groups) section. - Create a new team with a name that identifies the company (e.g., "Team Client ABC"). - Add to the team only the agents who should access the contacts of that company. If the agent does not yet exist in the account, you can invite them later. 3. Restrict access to the company in the Companies module - In the main menu, access the Companies module. - Locate the company whose contacts should be isolated and click to edit. - On the edit screen, look for the Access or Authorized teams section. Select the team created in step 2. - Save the change. From that moment on, only members of the selected team will be able to view that company and all contacts linked to it in the CRM. Agents from other teams will not see the company or its contacts. 4. Invite the agent with the correct role and team - If the agent is not yet in the account, go to Settings → Agents (or Users) and use the Invite agent option. - In the invitation, select the custom role created in step 1. - After the agent accepts the invitation, access team management and add them to the dedicated team from step 2. If the agent already exists in the account, edit their profile to change the role and make sure they are only in the desired company's team. 5. (Optional) Also restrict conversations to the company's inbox So that the agent only sees conversations from the contacts of that company, you can associate the team with a specific inbox: - Go to Settings → Inboxes. - Locate the inbox linked to the company's channel (e.g., corporate WhatsApp). - Click on the inbox Settings and access Collaborators. - Select the team created instead of individual agents. - Save. This way, the agent will have access only to the company's contacts in the CRM and to conversations that arrive through the designated channel. Who this configuration is useful for - White label resellers who need to give agents of each end client access only to the contacts of their own company, without exposing data from other clients. - Operations with sensitive data (financial, legal) that require total segregation between companies. - Outsourced teams that work for a specific corporate client and should not access the rest of the database. - Franchises or units that share the same Papo account but need isolation between contacts of each CNPJ. Frequently asked questions Can the agent still search for contacts from other companies in the CRM? No. Since the company is configured to be accessible only by the agent's team, they do not see other companies in the Companies module. Consequently, contacts linked to other companies do not appear for them, even if they use the search in the Contacts module. Do I need to create a custom role for each company? No. You can reuse the same custom role for multiple agents, as long as it grants access to the Contacts and Companies modules. The company restriction is done exclusively by associating the team with the company, not by the role. Can I restrict the agent to one company but allow them to see multiple inboxes? Yes. The contact restriction by company is independent of inboxes. You can associate the team with multiple inboxes, if desired, without affecting the limitation of contact visibility in the CRM. What happens if the agent belongs to more than one team? If the agent is in more than one team, they will see all companies and contacts associated with any of those teams. To maintain isolation, keep the agent in a single team. Is it possible to limit the agent to only read contacts, without editing? The custom role allows controlling modules, but granular read/write permissions within a module are not covered by standard roles. For that level of detail, consult the options available directly on the platform. How do I link contacts to a company in the CRM? In the Contacts module, when creating or editing a contact, you can associate it with a company previously registered in the Companies module. This way, the contact becomes part of that company's database and inherits the configured access restrictions. Read also - How to manage your contacts in Papo's CRM: search, creation, and update - How to create and manage agent teams in Papo Start for free and configure company access → With the first free user, you can already test the contact restriction by company and organize your operation with complete security.

How to cancel your Papo subscription and export your data before you leave

To cancel your Papo (https://papo.global/) subscription without losing important information, export conversation reports as CSV, set up a webhook to Google Sheets, and then request closure through the official support channel. Papo keeps your data for an indefinite period while the account is active, but retention after cancellation must be confirmed directly with support. Summary of the exit process | Step | Action | Result | | :--- | :--- | :--- | | 1. Export reports | Generate a conversation report by channel and export it to CSV. | Backup of metrics and service volume by source. | | 2. Set up webhook backup | Create a flow that sends new conversation data to Google Sheets. | Continuous copy of interactions while the account is still active. | | 3. Gather account information | Note the registration email, organization name, and connected channels. | Speed up the cancellation request. | | 4. Request cancellation | Get in touch through Papo's official support channel. | Subscription closure according to the current terms. | | 5. Confirm data deletion | Ask support about timelines and the post-cancellation retention policy. | Clarity on what happens to your history and contacts. | Why export before cancelling? While your account is active, Papo stores your entire conversation history and customer data in the CRM for an indefinite period — including messages from WhatsApp, Instagram, Telegram, email, and any other channels connected to the unified inbox. There is no automatic purge policy for inactivity. However, the platform's public materials do not detail what happens to this data after the subscription ends. That is why the recommendation is to make a copy of everything relevant to your operation before confirming the cancellation. What you can export in Papo | Data type | How to extract it | Format | | :--- | :--- | :--- | | Conversation report by channel | Reports module → export CSV. | CSV (opens in Excel, Google Sheets, etc.) | | Real-time conversation data | Flows module → webhook to Google Sheets (via Zapier, Make, or Apps Script). | Automatic rows in the spreadsheet | | Contacts and individual history | Search and filters in the CRM (name, email, phone, tags). | Manual lookup; bulk export not specified | How to export conversation reports by channel Papo's Reports module lets you generate a conversation report broken down by source channel and export the table to CSV. Follow these steps: 1. Go to the Reports module in the Papo dashboard. 2. Open the conversation report. 3. Set the desired period (Today, Last 7 days, Last 30 days, or a custom range). 4. Apply channel filters to select the sources you want to include (WhatsApp, Instagram, Facebook, email, etc.). 5. Check the columns with conversation volume, average response time, conversions, and SLA. 6. Use the export option to download the CSV file. The CSV reflects exactly the view that is visible in the report. You can repeat the process for different periods or channels and consolidate the files in an external spreadsheet. How to export conversation data to Google Sheets via webhook To keep an automatic copy of conversations while the account is still active, use Papo's Flows module to create an automation that sends the data to Google Sheets. The basic flow is: 1. Prepare the destination: in Google Sheets, create a spreadsheet and generate a webhook URL using an automation platform (Zapier, Make) or a Google Apps Script with the doPost function. 2. Create the Flow in Papo: go to Flows, add a trigger such as "New conversation" (or "Message received"), and select the desired inbox. 3. Configure the webhook action: enter the generated URL, the POST method, and define the JSON body with the conversation variables (contact name, channel, message text, agent, date). 4. Test and activate: use a test URL to validate the payload and then activate the flow. Once activated, every new conversation will be automatically recorded in your spreadsheet. This integration does not recover past history, but it ensures that the most recent interactions are saved before cancellation. How to request subscription cancellation Papo's help center does not define a single click path for cancelling. The procedure must be handled directly with the official support channel. To speed things up, gather the following beforehand: - The account's registration email. - The organization name or the connected WhatsApp number. - Whether there is more than one user or linked inbox. - Whether you need a period of access after the request. This way, the Papo team can confirm the procedure and the terms that apply to your case. What happens to your data after cancellation? Papo's public policy refers to storage while the account is active. There is no automatic definition of retention or deletion after closure in the available materials. Therefore: - Do not assume immediate deletion — the history may continue to be retained for a period defined in an internal policy. - Confirm in writing, if possible — ask support whether there is a remaining access period, whether the data can be exported, and when definitive deletion occurs. Who this guide is useful for - Companies that are winding down an operation or switching tools. - Teams that need to keep history for audits or commercial disputes. - Operations dealing with GDPR/LGPD that want to align data retention with the vendor. - Managers who want to plan their exit without losing access to strategic information. Frequently asked questions Does Papo automatically delete my data after a period of inactivity? No. While the account is active, the platform states that conversation history and CRM data are kept for an indefinite period, with no automatic purge policy for inactivity. What happens to contacts and conversations if I cancel? The public materials define retention only for active accounts. After closure, the timeline and deletion terms must be confirmed directly with Papo. Can I keep accessing the account after requesting cancellation? The remaining access period is not detailed in this help center. Confirm with official support whether there will be partial or full access after the request. How should I request cancellation? Use the official support channel indicated on Papo's website. There is no single click path in this help center that applies to all accounts. Does Papo allow exporting the entire history before cancelling? The possibility of bulk export is not specified in the public materials. You can export conversation reports as CSV and set up a webhook to Google Sheets; for other formats, consult support. Can I export just one channel to CSV? Yes. By applying the channel filter before exporting in the conversation report, the generated CSV file reflects only the selected view. Read also - How to export conversation data to Google Sheets via webhook - How to export service reports by inbox and agent as CSV Start for free → Try Papo with the first user at no cost and stay in full control of your data before making any decision.

How to set up email notifications for new leads in the CRM

To receive an email alert whenever a new lead is added to the Papo CRM, you can set up a Flow with the “Contact created” trigger and an email sending action. This way, the sales team is notified instantly with the lead’s data, without relying on manual checks. With this automation, every lead that enters the database — whether by import, form, or manual entry — generates a notification email for the responsible sales reps, speeding up follow-up and reducing response time. Configuration summary | Component | Role in the flow | Example of use | | :--- | :--- | :--- | | Flow (Flows/Chatbot) | Visual sequence of actions executed for each contact that meets the trigger. | Flow called “New lead alert”. | | “Contact created” trigger | Starts the flow automatically when a new contact is saved in the CRM. | Contact created via import, manually, or by integration. | | Email sending action | Triggers the notification email with the lead’s data. | Message with name, phone, email, and contact source. | | Contact variables | Dynamic fields that personalize the email content. | {{ contact.first_name }}, {{ contact.phone }}, {{ contact.source }}. | How it works: step by step 1. Create the Flow with the appropriate trigger In the Papo panel, go to the Flows / Chatbot module. Start a new Flow and give it a name such as “New lead notification”. In the editor, replace the default trigger with the Contact created event — it is available in the event list of the Flows module. This way, the flow will run every time a new contact record is inserted into the CRM, regardless of origin. 2. Configure the email sending action After the trigger, click “+” and choose the email sending action. Select the email inbox that will be used as the sender (you need to have an inbox configured in Settings → Inboxes). In the recipient field, enter the email address of the sales team or a distribution group. In the subject and body of the message, use the contact variables to automatically include the lead’s information. Example body: New lead received: Name: {{ contact.first_name }} {{ contact.last_name }} Phone: {{ contact.phone }} Email: {{ contact.email }} Source: {{ contact.source }} Created at: {{ contact.created_at }} You can also add a greeting or instructions for the team. 3. Adjust the conditions (optional) If you want to notify only a specific group of sales reps or leads from a certain source, insert a condition before sending the email. For example, check whether the contact tag is “hot lead” or whether the source is “website”. This way, the email is sent only for leads that meet the criterion. 4. Activate the Flow Review the sequence, save it, and change the Flow status to Active. From that moment on, every new contact created in the CRM will automatically trigger the flow, sending the notification email. Who is this automation recommended for? - Sales teams that need to be notified in real time about new leads, without relying on manual checks in the CRM. - Companies that capture leads through forms, landing pages, or list imports and want to speed up first contact. - B2B operations that work with active prospecting and want the sales rep to receive a lead summary as soon as the registration is completed. - Businesses that use Papo as a central contact hub and want to automate alerts for new records, regardless of the entry channel. Frequently asked questions Do I need to have an email inbox configured in Papo to send the notifications? Yes. You need to have at least one active email inbox on the platform. You can configure it in Settings → Inboxes, by adding an email account that will be used as the sender of the notifications. Can I send the email to multiple recipients? Yes, you can enter multiple email addresses in the recipient field, separated by commas, or use a distribution group address. You can also create different email actions in the same Flow to notify different teams based on conditions. Does the Flow work for contacts imported in bulk? Yes. Each contact included via import triggers the flow individually. This way, an entire list of leads generates an email notification for each new record. How do I include personalized lead information in the email body? Use the contact variables available in the Flow editor. Fields such as name, phone, email, source, and creation date can be inserted dynamically using the syntax {{ contact.field }}. The platform displays the list of available variables while editing the message. Is it possible to customize the sender of the notification email? Yes, the sender will be the email inbox you select in the sending action. You can configure different inboxes with different names and addresses, according to your operation’s needs. What happens if the notification email is not delivered? Papo records the sending status in the contact history. If a delivery failure occurs, you can check the error log in the reports module or in the Flow itself. For details about resend policies and limits, consult the platform documentation. See also - How to schedule automatic email sending of conversation reports - How to manage your contacts in the Papo CRM: search, creation, and update Start free now → Centralize channels, automate notifications, and speed up lead follow-up with Papo.