Integration Telegram (Telegram) 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 Telegram

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

API documentation — No.

Description

Not

Available fields
Id Name
update_id The ID of the webhook
channel_post.message_id Message ID
channel_post.sender_chat.id User ID
channel_post.sender_chat.title Channel Name
channel_post.sender_chat.type Chat Type
channel_post.chat.id User ID
channel_post.chat.title Channel Name
channel_post.chat.type Chat Type
channel_post.date The time of sending the webhook in timestamp format
channel_post.text Message text
+ You can add your fields that are in webhuk.

Description

Not

Available fields
Id Name
update_id The ID of the webhook
message.message_id Message ID
message.from.id User ID
message.from.is_bot Flag whether the user is a bot
message.from.first_name Username
message.from.last_name Last name of the user
message.from.username User's nickname
message.from.language_code User's language
message.from.is_premium The flag for whether the user has a Telegram Premium subscription
message.chat.id Message ID
message.chat.title The name of the group
message.chat.type Type: group
message.chat.all_members_are_administrators Flag whether all users are administrators
message.date The time of sending the webhook in timestamp format
message.text Message text
message.external_chat_user_id message.external_chat_user_id
message.external_chat_id message.external_chat_id
+ 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