Integration Telphin (Telfin) and DashaMail (Dasha Mail)
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 Telphin
Click on the name of the event to see the available fields.
API documentation — here.
Description
Not
Available fields
| Id | Name |
|---|---|
CallerExtension
|
The internal number is the initiator of the outgoing call |
CalledNumber
|
The number being called |
Duration
|
The duration of the call for each individual SubCallID in microseconds |
RecID
|
If conversation recording is enabled on the internal number, then its identifier is contained here |
CalledDID
|
The source of the call |
RemoteNumber
|
It can only be present in the flow of the “dial-in” event and indicates the external number that this call is associated with |
CallerIDNum
|
The caller's number that incoming calls are registered by default |
Bridged
|
The parameter indicates whether the call was accepted globally within the entire PBX by the user of the internal phone number |
Transfered
|
The parameter takes the value yes (the outgoing call occurred as a result of forwarding) |
CallStatus
|
The status of the call. A successful call has CallStatus=ANSWER |
CallBackID
|
Callback ID (ID of the outgoing call initiation via the API) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
CallerExtension
|
The internal number is the initiator of the outgoing call |
CalledNumber
|
The number being called |
Duration
|
The duration of the call for each individual SubCallID in microseconds |
RecID
|
If conversation recording is enabled on the internal number, then its identifier is contained here |
CalledDID
|
The source of the call |
RemoteNumber
|
It can only be present in the flow of the “dial-in” event and indicates the external number that this call is associated with |
CallerIDNum
|
The caller's number that incoming calls are registered by default |
Bridged
|
The parameter indicates whether the call was accepted globally within the entire PBX by the user of the internal phone number |
Transfered
|
The parameter takes the value yes (the outgoing call occurred as a result of forwarding) |
CallStatus
|
The status of the call. A successful call has CallStatus=ANSWER |
CallBackID
|
Callback ID (ID of the outgoing call initiation via the API) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
CallerExtension
|
The internal number is the initiator of the outgoing call |
CalledNumber
|
The number being called |
Duration
|
The duration of the call for each individual SubCallID in microseconds |
RecID
|
If conversation recording is enabled on the internal number, then its identifier is contained here |
CalledDID
|
The source of the call |
RemoteNumber
|
It can only be present in the flow of the “dial-in” event and indicates the external number that this call is associated with |
CallerIDNum
|
The caller's number that incoming calls are registered by default |
Bridged
|
The parameter indicates whether the call was accepted globally within the entire PBX by the user of the internal phone number |
Transfered
|
The parameter takes the value yes (the outgoing call occurred as a result of forwarding) |
CallStatus
|
The status of the call. A successful call has CallStatus=ANSWER |
CallBackID
|
Callback ID (ID of the outgoing call initiation via the API) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
CallerExtension
|
The internal number is the initiator of the outgoing call |
CalledNumber
|
The number being called |
Duration
|
The duration of the call for each individual SubCallID in microseconds |
RecID
|
If conversation recording is enabled on the internal number, then its identifier is contained here |
CalledDID
|
The source of the call |
RemoteNumber
|
It can only be present in the flow of the “dial-in” event and indicates the external number that this call is associated with |
CallerIDNum
|
The caller's number that incoming calls are registered by default |
Bridged
|
The parameter indicates whether the call was accepted globally within the entire PBX by the user of the internal phone number |
Transfered
|
The parameter takes the value yes (the outgoing call occurred as a result of forwarding) |
CallStatus
|
The status of the call. A successful call has CallStatus=ANSWER |
CallBackID
|
Callback ID (ID of the outgoing call initiation via the API) |
+ You can add your fields that are in webhuk.
Description
Not
Available fields
| Id | Name |
|---|---|
EventType
|
EventType |
CallID
|
CallID |
CallerIDNum
|
CallerIDNum |
CallerIDName
|
CallerIDName |
CalledExtension
|
CalledExtension |
CalledNumber
|
CalledNumber |
CalledExtensionID
|
CalledExtensionID |
CalledDID
|
CalledDID |
CallFlow
|
CallFlow |
CallStatus
|
CallStatus |
CallAPIID
|
CallAPIID |
+ 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 DashaMail
Click on the name of the action to see the available fields.
API documentation — here.
Request fields
| Id | Name |
|---|---|
from_email
|
From whom |
to
|
Whom |
subject
|
Topic |
message
|
Message |
Answer fields
| Id | Name |
|---|---|
transaction_id
|
Unique message id |
Request fields
| Id | Name |
|---|---|
from_email
|
From whom |
to
|
Whom |
subject
|
Topic |
message
|
Message |
event
|
Event code |
resend_period
|
The waiting period in days before the second letter |
Answer fields
| Id | Name |
|---|---|
transaction_id
|
Unique message id |
Integration setup plan Telphin with DashaMail
| 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
FAQ
How does the app differ from regular bundles?The application is not an alternative to bundles, but simply a preset set of bundles (template) for popular tasks to speed up setup.
Is it possible to change the logic of the created bundles?Yes. The created set of bundles can be customized according to your tasks or left unchanged if everything works as it should.
