**To automatically create tasks in the Papo Projetos module (https://papo.global/) from external events — such as a deal moving forward in the Kanban funnel — you can use the platform API together with automation tools like n8n or Zapier. The API allows you to query CRM cards and generate tasks in projects programmatically, eliminating the need for manual transfer between sales and operations.**

Integrating the sales pipeline with delivery execution is one of the main bottlenecks in B2B operations. When a deal card is moved to “Won” or reaches a specific stage, a series of actions must be triggered: onboarding, configuration, sending materials. With the Papo API, you can orchestrate this transition without human intervention, ensuring that every closed sale automatically generates a task in the correct project, with a defined assignee and deadline.

## Summary of the API automation flow

| Step | Action | Description |
| :--- | :--- | :--- |
| **1. Authentication** | Generate API key in the Papo dashboard | Credentials to authorize external calls. |
| **2. Funnel monitoring** | Query the Kanban cards endpoint | Identify deals that changed status (e.g., lead_status=won). |
| **3. Task creation** | Call the task creation endpoint in Projetos | Create a card in the project's Kanban board, linking the contact and sale data. |
| **4. Execution** | Operations team views the task in the Projetos module | Delivery follows the normal flow, with full traceability. |

## How task creation via API works

The Papo API exposes endpoints for the Kanban and Projetos modules. By combining these calls, you build an automated bridge between the CRM and delivery management.

### 1. Get your API keys

Before any integration, access the Papo dashboard, go to the **Developers** (or **API**) section, and generate a secret key (`sk_live_...`). This key will be used in the `Authorization: Bearer sk_live_...` header of all requests. The public key (`pk_live_...`) identifies your account, but authentication depends on the secret key. Store it in a safe place — it will not be shown again.

### 2. Monitor Kanban cards

The first step in automation is to detect when a deal moves forward in the funnel. The Kanban API allows you to list cards with status filters. For example, you can:

- Periodically query all cards with `lead_status=won` (won deals) that have not yet generated a task.
- Or, if your automation tool supports it, react to a card update webhook (check the official documentation for available events).

With a script or an n8n/Zapier workflow, you schedule a query to the card listing endpoint, filter the results, and trigger task creation only for cards that meet the criteria.

### 3. Create the task in the Project

With the card data (contact, deal title, value, etc.), you make a call to the task creation endpoint in Projetos. Typical parameters include:

- **project_id**: identifier of the destination project (e.g., “Onboarding” or “Post-sale deliveries”).
- **title**: task title, which can be built from the contact and deal name.
- **description**: context summary, extracted from the card.
- **priority**: urgent, high, medium, or low.
- **due_date**: calculated deadline, for example, 5 days after closing.
- **assignee**: person responsible for execution (can be fixed or defined by rule).

The API response confirms creation and returns the task ID. From then on, it appears on the chosen project's Kanban board, ready for the operations team.

### 4. Track execution

Once created, the task follows the normal Projetos module cycle: the team moves the card between columns, adds comments, and marks completion. The salesperson or manager can check progress without leaving the CRM, because Papo maintains traceability between the original deal and the delivery.

## Practical example with n8n (conceptual)

Although implementation details depend on the official API documentation (available at **papo.global/pt/docs**), the logical flow in a tool like n8n would be:

1. **Cron node**: triggers every 15 minutes.
2. **HTTP Request node (Papo API)**: GET to the Kanban card listing endpoint, filtering by `lead_status=won` and recent closing date.
3. **IF node**: checks whether there are new cards (not yet processed).
4. **HTTP Request node (Papo API)**: POST to the task creation endpoint, using the card data.
5. **Update node** (optional): marks the original card with a tag or custom field to avoid duplicates.

This same reasoning applies to Zapier, Make, or Python/JavaScript scripts.

## Who this integration is for

- **B2B operations with a consultative sales cycle**, where closing necessarily triggers a technical delivery or onboarding.
- **Companies already using Papo's Kanban and Projetos** and want to eliminate manual information transfer between teams.
- **CS and implementation teams** that receive dozens of new customers per week and need a standardized flow.
- **White-label resellers** that want to offer advanced automation to their clients, integrating the CRM with external project management systems.

## Frequently asked questions

### ### Do I need a webhook to detect changes in Kanban?
The Papo API offers endpoints for querying cards. If the official documentation includes webhooks, you can use them to receive real-time notifications. Otherwise, periodic polling is a viable and widely used alternative.

### ### Can I create tasks in any project via API?
Yes. As long as you have the active project ID, the task creation endpoint allows you to specify the destination project. You can keep separate projects for different delivery types (e.g., “Onboarding”, “Technical support”, “Customizations”).

### ### Does the task created via API inherit the deal contact?
Yes. When building the request, you can link the contact associated with the Kanban card. This way, the operations team accesses the conversation history and customer data directly in the task.

### ### Is it possible to set an assignee automatically?
Yes. The task creation endpoint accepts the assignee field. You can set a fixed value, use round-robin logic, or base it on card properties, such as the responsible salesperson.

### ### How do I avoid creating duplicate tasks?
It is recommended to keep external control (database, spreadsheet, or custom field on the card) to record which deals have already generated a task. Before creating a new one, the flow checks whether that card has already been processed.

### ### Where can I find the complete list of endpoints?
Detailed technical documentation, with all endpoints, parameters, and code examples, is publicly available at **papo.global/pt/docs**.

## Read also

- [How to use the Papo API to list conversations and send programmatic messages](/hc/papo/articles/how-to-use-papo-api-list-conversations-send-messages-programmatically)
- [Papo automations: Rules, Macros, Flows, and Webhooks – which one to use?](/hc/papo/articles/automations-papo-rules-macros-flows-webhooks)

---

**[Start for free →](https://chat.papo.global/app/auth/signup?papo_lp=home&utm_source=lp&utm_medium=landing&utm_campaign=home&utm_content=start-free&papo_lp_v=start-free)**

With Papo's free plan, you can already generate API keys and test task automation between Kanban and Projetos.