The operational decision
Distinguish generic webhook capability from a tested connection to the firm's system. Buy the specific intake workflow the firm needs, with clear limits and evidence. A product logo or broad feature list does not prove that an external calendar, case-management system or escalation route works for this firm.
Prepare the workflow
Ask which fields, operations and permissions are implemented, who maintains them and how errors reach staff; do not promise a native connector from a logo.
Example wording for approval
“Is this an existing tested connection for our proposed action, or custom work still requiring access and mapping? Please demonstrate with synthetic records only.”
Worked example
A supplier says it integrates with the firm's case-management platform because it can send a webhook. Ask whether the proposed workflow creates a contact, an inquiry or another record, which fields map across, and what happens when the destination rejects a field. Demonstrate with synthetic data. Generic outbound delivery is useful infrastructure, but it does not prove the firm's required operation works. Keep access approval, field mapping and maintenance ownership visible as separate dependencies in the scope.
Handoff record
Record these task-specific fields: system, requested operation, tested fields, maintenance owner.
Acceptance check
Offer a logo and an API description as evidence. The review should still require the exact write or read operation and its error handling.
Legal intake capacity calculator ↗
Try Ava with your business’s public information ↗