Attach an audio file to the call log in Pipedrive
A documented Pipedrive operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Attach an audio file to the call log
- POSTChanges data · CallLogs
api.pipedrive.com/callLogs/{id}/recordings
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Pipedrive operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Pipedrive operations
- Add a new userPOST · changes data
- Create a remote file and link it to an itemPOST · changes data
- Create a new WebhookPOST · changes data
- Link a remote file to an itemPOST · changes data
- Add a new goalPOST · changes data
- Add a new filterPOST · changes data
- Add a new deal fieldPOST · changes data
- Add a lead labelPOST · changes data
Questions
- Can HumDay attach an audio file to the call log in Pipedrive?
- Yes. This operation is published in Pipedrive's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Pipedrive data?
- Yes — this is a POST operation, so it changes something in Pipedrive. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Pipedrive account.
Where this came from
Read from the API description Pipedrive publishes themselves at developers.pipedrive.com/docs/api/v1/openapi.yaml. The description above is the provider’s own wording, not ours.