Three parts work together, all in Settings › Integrations: connections are the places outside Geo-CoWork we can reach, publishers are the events that can start work, and each publisher's automations say what to do when one happens.

Connections

Service	For	Signs in with
Amazon S3 and compatible storage	Importing new flights, receiving exports	An access key with list, read and (for exports) write on the prefix
Slack	Posting answers and alerts to a channel	Slack's own sign-in, when your server has a Slack app
Email	Sending answers and alerts to people	Built in: every organization has it
Webhook	Work-order systems and anything else with an HTTP endpoint	A header, an HMAC signature or basic auth

A connection is tested before it's saved, so a wrong key or a typo in a URL shows up at once.
Credentials are encrypted with your organization's own key. After saving, the app shows only a hint (the last characters), never the secret.
My connections are yours; shared ones, which Owners and Admins manage, can be used by everyone in the organization.
A webhook's body is a JSON template with placeholders such as {{task.title}} and {{feature_count}}, so it fits the system on the other end. Its answer can carry a reference (a ticket number), which we keep with the task.
We only call public internet addresses: a URL that points at a private network is refused.

Publishers: what can start work

Geo-CoWork events: a file finished uploading, or a file is ready (checked, or processed).
Schedules: every few hours or days, once at a set time, or a cron expression.
An S3 folder: we look for new objects under a prefix every five minutes. Files already there when you set it up don't count.
An inbound webhook: your system posts to an address we give you, signed with its secret (HMAC, with a timestamp that must be within five minutes). A repeated event is recognised and ignored.

Automations: what to do

Import the new file into a project, and process it when it's a vector file.
Re-run a follow-up question (below).
Notify through a connection: a Slack channel, people by email, or a webhook.

Every event and what each automation did with it is in the publisher's event log. A step that fails is tried again a minute later, then four minutes after that; if the third try fails too, it's marked as failed, and Retry in the log starts it again.

Follow-up questions

Follow up under an answer saves the question to be asked again, on a schedule or when an event arrives, for example every Monday, or whenever a new flight lands in the S3 folder. Each run starts a fresh conversation, shares the answer as a link that lasts 30 days, and posts it where you chose. A follow-up runs at most 24 times a day, so a noisy folder can't use up your credits.

Tasks

Create task under an answer turns the highlighted features into a task with a title, an assignee from your organization and a due date. The project's Tasks page lists them. With a work-order connection, the task is also sent there, with its features, and the reference the other system returns is shown on the task.