langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 20:45:26 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

feat: Add Plivo SMS and Verify API integrations #21919

New Issue
Closed
opened 2026-02-21 20:14:51 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:14:51 -05:00
Owner
Copy Link
Copy Source

Originally created by @navi- on GitHub (Jan 27, 2026).

Feature Request

Description

Add Plivo as a communications provider for SMS messaging and phone verification (OTP) in Dify.

Use Cases

  1. SMS Tool for Workflows/Agents: Enable AI agents and workflows to send SMS notifications, alerts, and messages via Plivo API
  2. Phone Verification: Add phone-based authentication using Plivo Verify API for:
    • SMS OTP delivery
    • Voice OTP delivery (for accessibility and landlines)
  3. SMS Notifications: System notifications via SMS as an alternative to email

Proposed Solution

  • New SMS Tool Provider at api/core/tools/builtin_tool/providers/plivo_sms/
  • SMS Extension at api/extensions/ext_sms.py for Plivo client management
  • Integration with AccountService for phone-based login
  • Support for both SMS and Voice channels for OTP delivery

Why Plivo?

  • No existing CPaaS (Communications Platform as a Service) integrations in Dify
  • Plivo offers competitive pricing and global coverage
  • Supports SMS, Voice, and WhatsApp channels

Additional Context

This is a greenfield integration opportunity - Dify currently has no telephony or SMS providers integrated.

Originally created by @navi- on GitHub (Jan 27, 2026). ## Feature Request ### Description Add Plivo as a communications provider for SMS messaging and phone verification (OTP) in Dify. ### Use Cases 1. **SMS Tool for Workflows/Agents**: Enable AI agents and workflows to send SMS notifications, alerts, and messages via Plivo API 2. **Phone Verification**: Add phone-based authentication using Plivo Verify API for: - SMS OTP delivery - Voice OTP delivery (for accessibility and landlines) 3. **SMS Notifications**: System notifications via SMS as an alternative to email ### Proposed Solution - New SMS Tool Provider at `api/core/tools/builtin_tool/providers/plivo_sms/` - SMS Extension at `api/extensions/ext_sms.py` for Plivo client management - Integration with AccountService for phone-based login - Support for both SMS and Voice channels for OTP delivery ### Why Plivo? - No existing CPaaS (Communications Platform as a Service) integrations in Dify - Plivo offers competitive pricing and global coverage - Supports SMS, Voice, and WhatsApp channels ### Additional Context This is a greenfield integration opportunity - Dify currently has no telephony or SMS providers integrated.
yindo added the 💪 enhancement label 2026-02-21 20:14:51 -05:00
yindo closed this issue 2026-02-21 20:14:51 -05:00
yindo commented 2026-02-21 20:14:52 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jan 27, 2026):

You should submit it as a plugin. Please refer to the documentation at https://docs.dify.ai/en/develop-plugin/getting-started/getting-started-dify-plugin for plugin submission. Our main repository no longer accepts third-party plugin submissions. You should package the developed plugin and submit it to this repository: https://github.com/langgenius/dify-plugins/pulls

@crazywoola commented on GitHub (Jan 27, 2026): You should submit it as a plugin. Please refer to the documentation at https://docs.dify.ai/en/develop-plugin/getting-started/getting-started-dify-plugin for plugin submission. Our main repository no longer accepts third-party plugin submissions. You should package the developed plugin and submit it to this repository: https://github.com/langgenius/dify-plugins/pulls
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#21919
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?