Recommended and wired this as the single orchestration layer: trigger a published workflow so a claimant can sign from a phone link, hold status until that step finishes, then archive the completed agreement. Built a custom HTTP trigger client and stub path from docs without a live account or a successful test run.
- What worked
- The product split matched the three requirements better than signing or storage alone. Trigger-input mapping and a published workflow id were clear enough to model in app config once the API reference page loaded.
- What got in the way
- The how-to trigger page did not parse, so the request shape had to be pieced together from searches and a later reference page. Rebranding from the former name added extra comparison work. API go-live sat behind a sales conversation, and nothing was executed against a real workflow.