Integration Tire service and Planfix (Planfix)

Connection in 5 minutes, 30 days on tests, try.

Accepted webhooks
Done actions
New clients

Try 30 days free

Free Turnkey setting, Instructions.

What data can be transmitted from: from_Service to: to_Service

Important: Please note that the presence of events and actions between the two services does not guarantee a solution your task - the available events and actions may not connect with each other in the way you need.

If you cannot independently determine whether these events and actions will be able to solve your problem; contact support or use the Full construction setting.

Events c Шинсервис

Click on the name of the event to see the available fields.

API documentation — No.

There are no events, try Change to replace the services.

If you haven't found the right event, but the service has the right webhook, then use the universal connector "Including webhuk". It will be possible to tie the logic of bundles to any field that comes in the webhook.

Actions in Planfix

Click on the name of the action to see the available fields.

API documentation — No.

Request fields
Id Name
task.title Task name
task.description Task description
task.importance The urgency of the task
task.statusSet The task process
task.checkResult Checking the result
task.owner.id ID of the user who created the task
task.parent.id ID of the parent task
task.project.id Project ID
task.client.id Counterparty ID
task.beginDateTime Date/time the task was created. By default, the current value is
task.startDate Start date
task.startTime Start time
task.endDate Completion date
task.endTime Shutdown time
task.isSummary The task is cumulative
task.duration Duration of the task
task.durationUnit The unit of measurement of duration
task.workers.users.0.id Task performer 1
task.workers.users.1.id Task performer 2
task.workers.users.2.id Performer of 3 tasks
task.workers.groups.0.id Task group 1 performers
task.workers.groups.1.id Group of performers 2 tasks
task.workers.groups.2.id Group of performers 3 tasks
task.members.users.0.id Participant of the 1st task
task.members.users.1.id Participant 2 tasks
task.members.users.2.id Participant 3 tasks
task.members.groups.0.id Group of participants 1 tasks
task.members.groups.1.id Group of participants 2 tasks
task.members.groups.2.id Group of participants 3 tasks
task.auditors.users.0.id Auditor 1 tasks
task.auditors.users.1.id Auditor 2 tasks
task.auditors.users.2.id Auditor 3 tasks
task.auditors.groups.0.id Group of auditors 1 tasks
task.auditors.groups.1.id Group of auditors 2 tasks
task.auditors.groups.2.id Group of auditors 3 tasks
Answer fields
Id Name
task.id ID of the created task
task.general The end-to-end number of the created task

Request fields
Id Name
silent Sending notification of changes
task.id Task ID
task.general Task number (if specified, used instead of id)
task.title Task name
task.description Task description
task.importance The urgency of the task
task.statusSet The task process
task.checkResult Checking the result
task.owner.id ID of the user who created the task
task.parent.id ID of the parent task
task.project.id Project ID
task.client.id Counterparty ID
task.startDate Start date
task.startTime Start time
task.endDate Completion date
task.endTime Shutdown time
task.isSummary The task is cumulative
task.duration Duration of the task
task.durationUnit The unit of measurement of duration
task.workers.users.0.id Task performer 1
task.workers.users.1.id Task performer 2
task.workers.users.2.id Performer of 3 tasks
task.workers.groups.0.id Task group 1 performers
task.workers.groups.1.id Group of performers 2 tasks
task.workers.groups.2.id Group of performers 3 tasks
task.members.users.0.id Participant of the 1st task
task.members.users.1.id Participant 2 tasks
task.members.users.2.id Participant 3 tasks
task.members.groups.0.id Group of participants 1 tasks
task.members.groups.1.id Group of participants 2 tasks
task.members.groups.2.id Group of participants 3 tasks