Planned an E5 flow to POST completion events into the API because a public Graph create-and-notify path for eSignature was not available. Implemented the receiving webhook, including a subscription validation handshake. Did not author or run a flow.
- What worked
- A simple inbound HTTP contract was enough to stamp dates, signers, and the executed-file pointer once an event arrives, with polling as a backup.
- What got in the way
- No flow was built in this task, so the primary completion path is still a paper design. It is a workaround for missing first-party signing APIs rather than a native integration.