Connection in 5 minutes, 30 days on tests, try.
Free Turnkey setting, Instructions.
Click on the name of the event to see the available fields.
API documentation — No.
Not
Id | Name |
---|---|
id
|
Reception ID |
admission_date
|
Date of admission |
description
|
Description |
client_id
|
Client ID |
patient_id
|
Pet ID |
user_id
|
Doctor's ID |
type_id
|
The purpose of applying for an appointment |
admission_length
|
Duration of admission |
status
|
Admission status |
clinic_id
|
Clinic ID |
direct_direction
|
direct_direction |
creator_id
|
The ID of the user who created the reception |
create_date
|
Date of creation of the reception |
escorter_id
|
escorter_id |
reception_write_channel
|
Appointment channel |
is_auto_create
|
Indicates that the reception was created automatically |
invoices_sum
|
Invoice amount |
pet.id
|
Pet ID |
pet.owner_id
|
Pet owner's ID |
pet.type_id
|
Pet type ID |
pet.alias
|
Nickname |
pet.sex
|
Paul |
pet.date_register
|
Registration date (format Y-m-d H:i:s) |
pet.birthday
|
Date of birth (Y-m-d format) |
pet.note
|
Note |
pet.breed_id
|
Breed ID |
pet.color_id
|
Color ID |
pet.deathnote
|
Cause of death |
pet.deathdate
|
Date of death (Y-m-d H:i:s format) |
pet.chip_number
|
Chip number |
pet.lab_number
|
Laboratory number |
pet.status
|
Pet Status |
pet.picture
|
Picture |
pet.weight
|
Weight |
pet.edit_date
|
Date of editing (format Y-m-d H:i:s) |
pet.pet_type_data.id
|
Pet type ID |
pet.pet_type_data.title
|
The name of the pet type |
pet.pet_type_data.picture
|
A picture of a pet type |
pet.pet_type_data.type
|
Pet type Code |
pet.breed_data.id
|
Pet Breed ID |
pet.breed_data.title
|
The name of the pet's breed |
client.id
|
Client ID |
client.address
|
Customer's address |
client.phone_prefix
|
Customer's country code |
client.home_phone
|
The client's home phone number |
client.work_phone
|
The client's work phone number |
client.cell_phone
|
The client's mobile phone |
client.fax
|
Client's fax |
client.note
|
Customer's Note |
client.type_id
|
Type of client |
client.how_find
|
How did you find a client |
client.balance
|
Customer's balance |
client.email
|
Client's email address |
client.city
|
The client's city |
client.city_id
|
Client's city ID |
client.date_register
|
Date of registration of the client |
client.zip
|
The postal code of the client |
client.last_name
|
Client's last name |
client.first_name
|
Client's name |
client.middle_name
|
Patronymic of the client |
client.status
|
Client status |
client.passport_series
|
Customer's passport details |
client.lab_number
|
The client's laboratory number |
client.street_id
|
Customer's street ID |
client.apartment
|
The number of the client's house and apartment |
client.unsubscribe
|
The "unsubscribed from notifications" flag of the client |
client.number_of_journal
|
The number of the client's log |
wait_time
|
Waiting time |
+ 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.
Click on the name of the action to see the available fields.
API documentation — No.
There are no actions, try Change to replace the services.
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.
Ready-made customized bundles for popular business tasks