Repository navigation
Update CALL-E plugin to 0.2.2 - #3366
Merged
Merged
Conversation
Contributor
Author
|
Resolved — verified 2026-10-19 06:29:32 UTC: Pre Check Plugin #8062 completed successfully on 2026-10-17 (attempt 2), and this PR merged at 2026-10-19 04:40:25 UTC. The official Marketplace API reports 0.2.2 as active, and the 0.2.2 download returns HTTP 200. The earlier CI approval request is resolved. |
crazywoola
approved these changes
Oct 19, 2026
crazywoola
left a comment
Member
There was a problem hiding this comment.
Verified publication eligibility for 1ac49b8: Pre Check Plugin and PR Risk Label both passed for this revision, and this PR is open and ready for review. Inspected the submitted manifest, README, and relevant tool/provider source: the plugin provides outbound phone-call creation and result retrieval, with no Web3 functionality found. This approval covers publication eligibility.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plugin Submission
Plugin information
Submission type
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 remainsderekwang2002/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
cursortoafter. The README covers migration. Historical v1 Call IDs stay with their original interface.Risk level
Required checks
.envfiles,.gitdirectories, virtual environments, caches, logs, or IDE files.PRIVACY.mdor a hosted privacy policy, andmanifest.yamlreferences it.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=falseandconfirm_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. SeePRIVACY.mdfor data handling.Local validation
.venv/bin/python -m pytest -qpasses 102 tests.python -m compileall -q provider tools utils main.pyandgit diff --checkpass.manifest.yamldiffers: version,repo, andcontact. Runtime sources and tool definitions are unchanged.dify-marketplace-toolkitmanifest validator at commit57a21d1304b1108df3e6b90a15a4f5dd9f0915f9, run locally with yq 4.54.1 against the extracted 0.2.2 package, reports zero errors and zero warnings.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.
Verified 2026-10-19 06:29:32 UTC: CALL-E 0.2.2 is active and downloadable from Dify Marketplace. Marketplace PR #3366 merged at 2026-10-19 04:40:25 UTC. Pre Check Plugin #8062 completed successfully on 2026-10-17 (attempt 2).
The official plugin API reports
latest_version=0.2.2,status=active, andversion_updated_at=2026-10-19T04:41:09.932753Z. The 0.2.2 download returned HTTP 200 (application/zip, 28,728 bytes); itsmanifest.yamlconfirms version0.2.2, authorderekwang2002, namecall_e, and maintainer J.Jason (@JJasonSun).At the initial 2026-10-19 06:29:32 UTC check, the Marketplace page showed
0.1.9, differing from the live API and downloadable package. Rechecked on 2026-10-19 at 06:40–06:41 UTC using rendered Chrome and fresh HTML: the detail page shows0.2.2, Version history starts with0.2.2, and the default Install link targetsderekwang2002/call_e:0.2.2@a83b3e27466d799b74f858f8a263360504005bb63e1b1ab54d7a37f036058ff3. The API remainsactive/0.2.2; the earlier discrepancy has cleared. Its cause remains unknown. This availability check did not install the plugin or rerun functional or call tests.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.