CALL-E 0.3.0 — Custom Call Result Schemas

CALL-E 0.3.0 lets Dify workflows request their own business result fields.

• create_call and create_and_wait accept optional Result Schema JSON. Blank input keeps the built-in fields; custom schemas support up to 32 flat scalar fields.
• Call results retain custom field values and types through creation, waiting, and retrieval, including phone-named business fields. Destination, metadata, and error phone fields remain masked. Business results and transcript text may contain personal data.
• An importable appointment workflow reads the result object and routes confirmed, rescheduling, and unresolved outcomes. Custom keys are read through a Code node and do not automatically appear in Dify's variable picker.

Existing workflows can keep their inputs and result paths. Workflows that adopt custom schemas require this version or later.

Validation: 191 tests, Python compilation, and both CI checks pass. The release package contains 28 runtime, documentation, and example files and matches the reviewed source byte for byte. Final-package Dify CE checks cover saved default/custom request replay, typed custom business fields from an official-hotline call, and Get Call. Dify Cloud Sandbox verification also passed: official-hotline call completion, default fields, metadata round trip, and identical results from same-key replay.

Package: call_e-0.3.0.difypkg

SHA-256: 417a243cfd49dea1802aa0e0112f0352eb5842d7ed01368e41d1d937e7d52fc5