Post-call functions
Post-call functions run once at finalization — with the call’s final variables, its summary and the result of post-call analysis. The block has no overall budget, but there is a cap on how long it waits for the analysis.Run condition
A post-call function form has a Run only if field — empty by default, which means “always”. The condition uses the same language as transition conditions between nodes:
The condition sees the same variables as the request, including the results of functions executed earlier in this block (in the rows above) — for example
{{crm_close_success}}. The node_visited() and goals_completed() functions are not available here: the conversation is already over. A condition with an error prevents the agent from being saved.
The card shows an “if …” line with your expression under the name. A false condition means the function is not called at all: the history gets an event with the status “skipped” and the note “skipped by condition”, and no result variables are written.

What the variables hold
Besides the final call variables, post-call functions get two reserved ones.call — the call summary: the same object that goes into the call_ended webhook, but without the recording data. It holds the channel, direction, numbers, duration (call.duration), final status (call.call_status) and end reason (call.status_reason), the transcript and the call variables.
analysis — the post-call analysis result:
The keys are always present; the meaningful fields are filled only when
status = "done". Without an analysis call_successful is empty, so neither == true nor == false matches it: for such calls check {{analysis.status}}, for example {{analysis.status}} != "done".
Nested values are reached with a dot, and they work not only in the condition but inside the request itself: {{analysis.summary}} can go into the message body for a manager, {{call.duration}} into a CRM field. A whole dictionary ({{call}}, {{analysis}}, {{analysis.sentiment}}) is substituted as JSON.
When they run
Thecall_ended webhook goes out right after the call ends, before the post-call functions. The functions themselves wait for the conversation analysis to finish, but no longer than 60 seconds (the value is a platform setting).
- Post-call analytics is off, or the analysis was skipped by outcome — the functions run immediately with
analysis.statusset toskipped. - The analysis is still queued — the block is deferred and runs as soon as the analysis is done; the delay after that is seconds.
- The analysis did not finish in time — the functions run with the status stored at that moment:
pendingorprocessing. A late result will not re-run them.
Where to see the result
In History, in the call card, each function has a Post-call function event with its status, HTTP response code and execution time. If there is no analytics result, the event carries the note “without analytics result”. Result variables are not saved to the call — only the events remain. The events are visible to administrators and developers with Show system events switched on. What each status means is on the History, limitations and troubleshooting page.Testing a condition without a call
The analytics result does not exist before the call, so a trial run of a post-call function is given a stub. Expand the Analytics stub above the test buttons: it has the Call successful toggle, a Sentiment selector, and a Summary field. Left unchanged, the stub represents a successful call with a finished analysis. Change it, run the test, and watch the line “Condition: met” or “Condition: not met” — it only appears when a condition is set. The stub also applies to Test the block. In a trial runcall.duration is 0, so duration conditions such as {{call.duration}} > 30 are not met.
