Skip to content

feat: add Twilio and WhatsApp connector examples - #7082

Open
anunaym14 wants to merge 2 commits into
mainfrom
am/connector-examples
Open

feat: add Twilio and WhatsApp connector examples#7082
anunaym14 wants to merge 2 commits into
mainfrom
am/connector-examples

Conversation

@anunaym14

Copy link
Copy Markdown
Member

No description provided.

@anunaym14
anunaym14 requested a review from a team as a code owner September 1, 2026 11:19

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

Devin Review found 6 potential issues.

1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

Devin Review

Comment thread examples/telephony/connectors/twilio_connector.py Outdated
Comment thread examples/telephony/connectors/whatsapp_connector.py

call_sid = form.get("CallSid", "")
caller = form.get("From", "")
logger.info(f"Inbound call {call_sid} from {caller}")

@devin-ai-integration devin-ai-integration Bot Sep 1, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟥 Twilio caller data leaks through logs

Calls write phone numbers, call identifiers, room names, and provider errors into log messages. Redaction cannot remove these sensitive values.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Phone numbers are masked to last-4 wherever logged, and provider payloads (Twilio REST error bodies, connector error messages) pass through a redaction step that masks any phone-number-like digit run before logging. Call SIDs and room names remain deliberately: they're opaque correlation identifiers, not PII, and removing them would make the example undebuggable.

call_id = call.get("id", "")
event = call.get("event", "")
direction = call.get("direction", "")
logger.info(f"Call event {event} ({direction}) for {call_id}")

@devin-ai-integration devin-ai-integration Bot Sep 1, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟥 WhatsApp customer data leaks through logs

Webhook and dial paths log call data, phone numbers, room names, provider payloads, and exceptions. Redaction cannot remove these sensitive values.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Numbers are masked in logs, participant identities are random short ids (the caller's number rides only in the proto field marked for redaction), and every provider payload that reaches a log — Meta error objects, status updates, connector error messages, unparseable bodies — passes through a redaction step that masks phone-number-like digit runs while preserving error codes and the fbtrace_id. Call ids and room names remain as opaque correlation identifiers.

Comment thread examples/telephony/connectors/twilio_connector.py Outdated
Comment thread examples/telephony/connectors/twilio_connector.py Outdated
@anunaym14
anunaym14 force-pushed the am/connector-examples branch 2 times, most recently from ccbf1d7 to d50bf29 Compare September 1, 2026 12:18
devin-ai-integration[bot]

This comment was marked as resolved.

@anunaym14
anunaym14 force-pushed the am/connector-examples branch 2 times, most recently from fe605b4 to 04f1c7a Compare September 1, 2026 13:20
@anunaym14
anunaym14 force-pushed the am/connector-examples branch from 04f1c7a to 6691001 Compare September 1, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant