What these pages cover
Each integration page documents one system as an automation surface rather than as a product: which events it can trigger on, which actions it exposes to an automation, what its API limits do to throughput, and which permissions the connection needs. That is the information that decides whether a workflow is a two-week build or a three-month one, and it is usually missing from vendor documentation, which describes features rather than operating constraints.
How to choose a starting system
Start from the system that already holds the record you want to keep correct, not from the one that is easiest to connect. If your quotes live in a CRM and your enquiries arrive on WhatsApp, the CRM is the system of record and the messaging channel is the trigger. Automations built the other way around tend to create a second, competing copy of the truth, which costs more to unwind later than the original manual work cost to run.
Where the boundary is
We connect systems through their supported APIs and official automation surfaces. We do not screen-scrape, drive a logged-in browser session as a substitute for an API, or work around a vendor's rate limits, because all three break silently on the vendor's schedule rather than on yours. When a system has no usable API for what a workflow needs, we say so during the audit and the workflow gets designed around a different system of record.
Discuss which one fits