---
title: Planfix
path: planfix
icon: briefcase
description: "Planfix CRM action parameters, customer consent and result verification."
---

# Planfix

First [connect your account and select the API token owner](../../integrations/CRM/planfix.md).

| Action | Bot inputs | Result |
|---|---|---|
| Find contact | Phone with country code or email | Exact match count, contact IDs and names |
| Create or update contact | First name, phone or email, consent; an existing contact ID can be supplied for updates | Contact ID and whether it was created or updated |
| Create CRM request | Contact ID, title, description and consent | New or existing active CRM task ID |
| Update status | CRM task ID and an approved status | Confirmed update or waiting for confirmation |
| Create task | Subject, date/time with timezone offset, contact or CRM task, consent | Task ID; the supplied CRM task becomes its parent |
| Add comment | Record type: contact, CRM request or task; record ID and text | Comment ID |
| Get record link | Record type and ID | Link to an existing record in the connected account |

The bot obtains consent before saving new customer data. Templates, process, assignee and approved statuses come from the individual action settings. Amount and currency changes are unavailable in this version.

## Settings for individual actions

Select the Planfix connection inside each operation and configure its parameters:

- **Find contact** — duplicate matching policy.
- **Create or update contact** — contact template, find-only or creation mode, and duplicate matching policy.
- **Create CRM request** — process, task template, initial status, optional assignee and task due interval in hours.
- **Update status** — process and approved statuses.
- **Create task** — process, task template, initial status and optional assignee; the bot supplies the deadline when executing the action.
- **Add comment** — process used to check task ownership.
- **Get record link** — no additional CRM settings.

Lists come from the connected account. After changing the process, select its template and statuses again. The token owner and silent mode remain in connection settings. Creating a template bot saves its selected parameters into that bot's actions only.

## Recommended sequence

1. Collect the customer's name, contact details and request.
2. Search by exact phone, then email.
3. Escalate multiple matches or conflicting identities to a manager.
4. Obtain consent and save the contact.
5. Create a CRM request or use the existing active task.
6. Add a comment and manager follow-up task when needed.
7. Report the result only after confirmation.

Use IDs returned by earlier actions. Do not invent record IDs. Approved status IDs and labels come from the **Update status** action settings.

Write previews validate parameters, mapping and referenced records without changing Planfix. Search and record-link actions read live data.

Repeating a write with the same execution identifier does not create another record after an unknown result. A new request could create a duplicate: inspect the external record first.

These actions do not send messages to the customer through Planfix. The connected ChatRex messaging channel delivers the reply.