[JJasonSun]

Plugin Submission

Plugin information

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

Submission type

• New plugin
• Version update

What changed

Call creation accepts optional custom result schemas with up to 32 flat scalar fields. Empty input keeps the built-in fields. Create, wait, and get responses preserve custom business values and types. An importable appointment example reads these fields and routes explicit confirmation, rescheduling, and unresolved results.

Create Call / Create and Wait
  validate custom schema or use default
  CALL-E result -> business fields -> workflow branch

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 Development Guidelines.
• 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

CALL-E receives the destination phone number, task, optional metadata, and result schema. Live calls require both explicit live-call controls and a saved idempotency key. The administrator supplies a CALL-E API key and backend base URL; requests carry credentials only to that configured backend, use bounded timeouts, and do not follow redirects. The provider credential probe does not create calls.

Destination, metadata, and error phone fields are masked. Call business results retain their original values and types, including phone-named fields; results, summaries, and transcript text may contain personal data. The plugin does not execute user code, SQL, shell commands, or browser actions and bundles no executable binaries. High risk is selected for credential handling and an administrator-configured backend.

Local validation

• python -m pytest: 191 passed.

• python -m compileall provider tools utils main.py: passed.

• Dify Plugin CLI 0.6.12 packaging: passed. The package contains 28 runtime, documentation, and example files, checked against source byte for byte.

• Final-package Dify CE 1.17.1: default/custom saved requests replay without changing Call IDs; typed business values from an official-hotline call are preserved by waiting and Get Call.

• Final-package Dify Cloud Sandbox: active version 0.3.0; a cache-cleared four-node workflow completed an official-hotline call and replayed the same business key. Both nodes returned the same Call ID and full parsed result, with result_status=available, call_outcome=completed, error=null, no timeout, all requested metadata returned, and the original nine default result fields.

Reviewer notes

This PR adds only derekwang2002/call_e/call_e-0.3.0.difypkg. Existing workflows that leave Result Schema JSON empty keep their schema and output paths. Workflows using custom fields need version 0.3.0 or later. Custom keys are accessed in a Code node, not generated as individual Dify variable-picker entries.

Release: https://github.com/CALLE-AI/call-e-dify-plugin/releases/tag/v0.3.0

Package SHA-256: 417a243cfd49dea1802aa0e0112f0352eb5842d7ed01368e41d1d937e7d52fc5