Log Call Note: Aircall action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Call ID callId	string	Required	12345
Comment content	string	Required	Note to attach to the call.

Sample request

{
  "callId": "12345",
  "content": "{{trigger.content}}"
}

Returns

{
  "call": {
    "id": 12345,
    "comments": [
      {
        "id": 9,
        "content": "Follow up next week"
      }
    ]
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Log Call Note.

What does the Log Call Note action do in Aircall?

Appends notes, tags, or disposition codes to a specific call after it ended. Useful for "AI-summarised post-call notes from a transcription service → log back to the Aircall call record" workflows that keep the call history annotated.

What inputs does Log Call Note require?

Required: Call ID, Comment. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Aircall returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Log Call Note support batch operations?

Yes. Run Log Call Note inside a Loop node to process arrays. Tiny Command handles Aircall's rate limits automatically so you don't have to throttle manually.

More actions