Integration Notion (Notification) and AmoCRM (Amo Cpm)
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
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 Notion
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 AmoCRM
Click on the name of the action to see the available fields.
API documentation — here.
Request fields
| Id | Name |
|---|---|
name
|
Name |
status_id
|
Stage |
pipeline_id
|
Funnel |
price
|
Budget |
responsible_user_id
|
Responsible |
tags
|
Tags |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
name
|
Name |
status_id
|
Stage |
pipeline_id
|
Funnel |
price
|
Budget |
responsible_user_id
|
Responsible |
tags
|
Tags |
contact.name
|
Contact Name |
contact.email
|
Contact's email address |
contact.phone
|
Contact's phone number |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
name
|
Name |
status_id
|
Stage |
pipeline_id
|
Funnel |
price
|
Budget |
responsible_user_id
|
Responsible |
tags
|
Tags |
contact.name
|
Contact Name |
contact.email
|
Contact's email address |
contact.phone
|
Contact's phone number |
company.name
|
Company Name |
company.email
|
Company email |
company.phone
|
Company phone number |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
source_name
|
Name of the application source |
pipeline_id
|
ID of the funnel that contains the unassembled |
leads.name
|
Name of the transaction |
leads.price
|
The amount of the transaction |
leads.tags
|
Transaction Tags |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
name
|
Contact Name |
responsible_user_id
|
ID of the user responsible for the contact |
am_linked_deal_id
|
ID of the related transaction |
Answer fields
| Id | Name |
|---|---|
id
|
Contact ID |
Request fields
| Id | Name |
|---|---|
name
|
Name |
first_name
|
Contact Name |
last_name
|
Contact's last name |
email
|
|
phone
|
Telephone |
Answer fields
| Id | Name |
|---|---|
id
|
Contact ID |
Request fields
| Id | Name |
|---|---|
name
|
Company Name |
responsible_user_id
|
ID of the user responsible for the company |
am_linked_deal_id
|
ID of the related transaction |
am_linked_contact_id
|
ID of the associated contact |
Answer fields
| Id | Name |
|---|---|
id
|
Company ID |
Request fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
name
|
Name |
status_id
|
Stage |
pipeline_id
|
Funnel |
price
|
Budget |
linked_company_id
|
Company ID |
main_contact_id
|
Contact ID |
source_data
|
source_data |
responsible_user_id
|
Responsible |
Request fields
| Id | Name |
|---|---|
id
|
Contact ID |
Answer fields
| Id | Name |
|---|---|
id
|
Contact ID |
name
|
Name |
first_name
|
Contact Name |
last_name
|
Contact's last name |
email
|
|
phone
|
Telephone |
responsible_user_id
|
Responsible |
Request fields
| Id | Name |
|---|---|
text
|
Task description |
element_id
|
ID of the linked transaction |
responsible_user_id
|
Responsible |
task_type
|
Type of task |
complete_till
|
The date when the task should be completed |
Answer fields
| Id | Name |
|---|---|
id
|
Task ID |
Request fields
| Id | Name |
|---|---|
email
|
|
phone
|
Telephone |
status_id
|
Stage |
pipeline_id
|
Funnel |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
id
|
Transaction ID |
name
|
Name of the transaction |
status_id
|
Stage |
pipeline_id
|
Funnel |
price
|
The budget of the transaction |
tags
|
Tags |
Answer fields
| Id | Name |
|---|---|
id
|
Transaction ID |
Request fields
| Id | Name |
|---|---|
element_id
|
Transaction ID |
text
|
The text of the note |
Answer fields
| Id | Name |
|---|---|
id
|
Note ID |
Integration setup plan Notion with AmoCRM
| 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