---
title: "Connecting other tools"
description: "Maps, calendars, AI, messaging and the services your app needs to fit in."
canonical: "https://docs.automo.build/connect/connecting-other-tools"
---

# Connecting other tools

> Maps, calendars, AI, messaging and the services your app needs to fit in.

Few apps live alone. Automo Build connects to the tools you already use through integrations, so you do not have to build a bridge each time.

## Ways to connect

- **Integrations:** services such as payments, email, calendars or AI, connected by asking in the chat.
- **Webhooks:** your app calls another system when something happens.
- **Incoming requests:** another system calls your app, useful for notifying it about a change.

Ask for the outcome and describe the trigger: "when a booking is confirmed, create an event in the team calendar." Naming the tool is helpful but not required.

Want your own AI tool, such as Claude, ChatGPT or Cursor, to drive Automo Build? See [MCP](/mcp/overview).

## Popular combinations

- **Calendar** — bookings appear where the team already looks.
- **Messaging** — a message in a team channel when a form is submitted.
- **Maps** — addresses geocoded and shown on a map.
- **AI** — summaries, drafting, categorising and answering questions about your own content.
- **Spreadsheets** — a two-way sync while you are still deciding what the tool should be.

## Design for failure

Every outside service will fail eventually. Decide what your app should do:

- Show a friendly message and keep the record.
- Retry quietly in the background.
- Fall back to doing the work manually.

Never assume the outside system answered. Check the response and keep the user informed.

## Keeping it tidy

Each integration you add is something to maintain. Start with the one that makes the biggest difference, get it working, then add the next. An app with two reliable connections is better than one with six flaky ones.