Skip to main content

Checklist

AI Integration Planning Checklist

Choose the first integrations and map each one to a real workflow.

7 min read

Start with the work, not the app list

Name one recurring question, report, or follow-up path, then connect the systems it needs.

  • What changed since the last meeting?
  • Which work is stuck or missing follow-up?
  • Which metrics need a plain-language explanation?
  • Which updates should be drafted for review?

Choose the first tools and files

Churches can start with Planning Center; nonprofits with program or CRM systems. Add only the tools needed for one workflow.

  • Pick two to four systems for the first report or workflow.
  • Choose the specific accounts, properties, channels, sites, calendars, or files needed.
  • Avoid connecting everything before anyone knows what the workflow should do.
  • Document the owner for each connection.

Decide who can connect what

Define whether each connection belongs to the organization or a member before workflows run.

  • Which integrations are managed by admins?
  • Which members need to connect their own accounts?
  • Which tools and files are available to shared workflows?
  • Which sensitive systems require extra review?

Expand after the first workflow is useful

After one workflow is trusted, add only tools and follow-up paths that answer a missing need.

  • Add tools or files that answer a missing question.
  • Add delivery destinations where teams already work.
  • Add reviewed actions only after reporting is trusted.
  • Review access and owners as more workflows are added.

Checklist

Integration planning checklist

Name the first report, review, or follow-up process.

List the systems needed for that work.

Choose the specific accounts, files, calendars, or channels that should be available.

Decide who owns each connection.

Define which follow-up actions require review.

Ready to apply this guide?

Map the first workflow, sources, and approvals.