Making applications talk.
WHAT CONNECTION MEANS
One system sending information to another automatically.
WHAT MAKES IT POSSIBLE
An interface the system provides for that purpose.
WHAT TO ESTABLISH BEFORE ASSUMING IT CAN BE DONE
Whether both systems support it.
WHY
Many systems do not, and the automation cannot be built.
WHAT TO CHECK
Whether the automation platform supports both What actions each connection permits What limits apply
WHY LIMITS MATTER
Volume restrictions cause failures at exactly the busiest moment.
WHAT TO ESTABLISH
How many operations you will use, and what happens beyond the limit.
WHAT COMMON CONNECTIONS ARE USEFUL
Forms to records Payments to accounting Messages to task systems Calendars to notifications Records to documents Systems to messaging platforms
WHAT TO BE CAREFUL WITH
Connections that write to accounting systems Connections that send to customers Connections that delete anything
WHY
Errors there are visible and expensive.
WHAT TO ESTABLISH ABOUT CREDENTIALS
Which account the connection uses.
WHY IT MATTERS
A connection authenticated with a person's account stops when they leave.
WHAT TO USE
An account belonging to the business.
WHAT TO RECORD
Every connection, what it does, and what it uses to authenticate.
WHY
Undocumented automations are found only when they break.
WHAT TO REVIEW
Whether connections still work after any system change.
