feat: add Twilio and WhatsApp connector examples - #7082
Conversation
There was a problem hiding this comment.
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)
|
|
||
| call_sid = form.get("CallSid", "") | ||
| caller = form.get("From", "") | ||
| logger.info(f"Inbound call {call_sid} from {caller}") |
There was a problem hiding this comment.
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}") |
There was a problem hiding this comment.
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.
ccbf1d7 to
d50bf29
Compare
fe605b4 to
04f1c7a
Compare
04f1c7a to
6691001
Compare
No description provided.