Update CALL-E plugin to 0.2.2

[JJasonSun]

Plugin Submission

Plugin information

• Author: derekwang2002
• Maintainer: J.Jason (@JJasonSun)
• Plugin name: call_e (CALL-E)
• Version: 0.2.2
• Source repository: https://github.com/CALLE-AI/call-e-dify-plugin
• Contact: support@heycall-e.com

Submission type

• New plugin
• Version update

What changed

Adds version 0.2.2 for Calls API v2, with the source repository and support email declared in manifest.yaml. The README and plugin/provider descriptions credit maintainer J.Jason (@JJasonSun). Plugin ID remains derekwang2002/call_e.

The plugin sends one phone destination, validates a closed scalar result schema, reads results/errors/transcripts, and waits for result readiness for Calls and Goal Runs. It preserves accepted IDs on read failures and emits named workflow outputs alongside JSON.

Breaking changes from 0.1.x: creation nodes require a stable caller-supplied idempotency key. Bind it to a saved upstream call-request ID, including an upstream-generated UUID; reuse it and the original inputs for retries and workflow reruns. Update legacy result mappings, region/locale hints, and Goal catalog pagination from cursor to after. The README covers migration. Historical v1 Call IDs stay with their original interface.

Risk level

• Low risk
• Medium risk
• High risk

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
• All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Security and privacy notes

The plugin handles an API credential, destination phone numbers, tasks, metadata, and call results/transcripts. It sends these to the configured CALL-E backend and can create outbound phone calls. The credential configuration accepts a custom HTTP(S) backend URL; operators must use a trusted backend because it receives the API key and call data. Requests do not follow redirects and use bounded timeouts. Credential validation does not create a call.

Live creation requires both dry_run=false and confirm_live_call=true. Missing or unsafe keys stop before a CALL-E request. The plugin does not execute shell commands, user code, SQL, browser automation, or filesystem operations, and does not request plugin KV storage. See PRIVACY.md for data handling.

Local validation

• Version 0.2.2 on Python 3.12 with Dify SDK 0.10.2: .venv/bin/python -m pytest -q passes 102 tests. python -m compileall -q provider tools utils main.py and git diff --check pass.
• Dify Plugin CLI 0.6.11 builds 27 files; all entries match source. Compared with 0.2.1, only manifest.yaml differs: version, repo, and contact. Runtime sources and tool definitions are unchanged.
• The official dify-marketplace-toolkit manifest validator at commit 57a21d1304b1108df3e6b90a15a4f5dd9f0915f9, run locally with yq 4.54.1 against the extracted 0.2.2 package, reports zero errors and zero warnings.
• Installed the exact 0.2.2 package on isolated Dify Community Edition 1.17.1 ARM64 and Dify Cloud Sandbox. Cleared workflow caches and replayed the original Calls and Goal Run requests on both hosts, including downstream same-request creation nodes. All four executions succeeded and retained original API/Billing or Goal Run/run/call IDs and available results. Cloud Calls metadata and named outputs matched the complete original result. No new calls were created.
• Prior real-call acceptance used the exact 0.2.1 package: Community Edition Calls and published Goal Run completed with available results and 7/8 transcript entries; Cloud published Goal Run completed with an available result and 9 entries. Each passed same-request replay and a cache-cleared workflow rerun. The 0.2.2 checks above verify installation and upgrade replay against those original calls.
• Package SHA-256: c0bda3b76aeafcc12de50b1ac40cf8ca75b467971c795604ee1c0335b8f178cb.

Reviewer notes

This PR adds one new package, version 0.2.2. Source PR CALLE-AI/call-e-dify-plugin#6 is merged; GitHub release 0.2.2 contains the same package. Installers for 0.2.0 and 0.2.1 have been withdrawn; their release notes and source tags remain available. Install 0.2.2.

The Marketplace pre-check run awaits repository-maintainer approval (action_required); it has not executed any jobs. The local manifest-validator result above does not represent a completed Marketplace CI run.

Acceptance covers Workflow/Tool nodes on Cloud and self-hosted Dify 1.17.1 ARM64. The isolated localhost Community Edition instance allowed unsigned local packages (FORCE_VERIFYING_SIGNATURE=false); no production signature setting changed. Agent/RAG applications, other deployment architectures, and production upgrades were not tested. Calls used the official automated test hotline, not a human-answer classification benchmark.

Separate Dify Workflow runs must receive the same saved upstream call-request ID and original inputs for a retry. The plugin does not generate a shared fallback key or deduplicate by phone/task.

[JJasonSun]

Could a maintainer please approve the pending CI workflow run for this PR? Pre Check Plugin #8062 is awaiting approval. Thank you.