Upgrade to ApiMonster from Zapier, Make, and other no-code services. We have optimal tariffs and a unique
Live chat support for your projects DS
CLUB.
Integration Ati.su (Ati Su) and Planfix (Planfix)
Connection in 5 minutes, 30 days on tests, try.
Accepted webhooks
Done actions
New clients
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.
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 Ati.su
Click on the name of the event to see the available fields.
API documentation — No.
Description
Not
Available fields
| Id | Name |
|---|---|
load_copy
|
A copy of the cargo |
deal
|
Order |
+ You can add your fields that are in webhuk.
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 |
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 |
|---|---|
action.description
|
Description of the comment |
action.task.id
|
Task ID |
action.task.general
|
Task number (if specified, used instead of id) |
action.taskNewStatus
|
New task status |
action.isHidden
|
The task is cumulative |
action.beginDateTime
|
Date/time the task was created. By default, the current value is |
Answer fields
| Id | Name |
|---|---|
action.id
|
ID of the added comment |
Request fields
| Id | Name |
|---|---|
contact.name
|
Name |
contact.midName
|
Middle name |
contact.lastName
|
Surname |
contact.post
|
Post |
contact.email
|
|
contact.phones.phone.0.number
|
Telephone |
contact.phones.phone.0.typeId
|
ID of the number type |
contact.phones.phone.0.typeName
|
Name of the room type |
contact.secondaryEmails.email.0
|
Additional email addresses |
contact.address
|
Address |
contact.description
|
Additional information |
contact.sex
|
Paul |
contact.site
|
Website |
contact.skype
|
Skype |
contact.facebook
|
|
contact.vk
|
Vkontakte |
contact.icq
|
ICQ Number |
contact.birthdate
|
Date of birth |
contact.signature
|
Signature |
contact.lang
|
Language |
contact.isCompany
|
Is a company |
contact.canBeWorker
|
It is displayed in the list of task participants |
contact.canBeClient
|
It is displayed in the list of contractors for the task |
contact.group.id
|
Contact group ID |
Answer fields
| Id | Name |
|---|---|
contact.id
|
ID of the added contact |
contact.userid
|
Contact ID (for an employee) |
contact.general
|
The end-to-end number of the added contact |
actionid
|
ID of the contact creation action |
Integration setup plan Ati.su with Planfix
| 1 | Configure the connection for: Service in Apimonster. |
| 2 | Configure Webhuk in: Service, indicating the link from Apimonster. |
| 3 | Configure the connection for: Service in Apimonster, indicating the login/password/token for access to the API. |
| 4 | Create a bunch. |
| 5 | Indicate as a data source: Service. |
| 6 | Create the required action for: to_Service, indicating in which fields: to_Service to transmit field values from: from_Service. |
| 7 | Configure filters for each step if necessary. |
| 8 | Test the bundles and make sure that they work according to the TOR. |
Or go through the full well on ApiMonster.
Check out other ApiMonster features
NoCodeStore - a store of ready-made no-code solutions
Ready-made customized bundles for popular business tasks
Whatsapp Tracker for Yandex.Metrica
Uploading conversions to Yandex.Metrica on the first message from Whatsapp
Is free