Automations and connections

Automations react to conversation or task events and run one or more steps. They can update Repliqo, send an approved automatic reply, create work, notify an external tool, or call a public webhook.

Paths: Settings → Connections and Settings → Automations

Connect an external account

Connect the account before adding a workflow step that uses it:

1. Open Settings → Connections.
2. Choose Trello, Slack, or Dropbox.
3. Complete the provider's authorization flow.
4. Give the connection an optional name when the workspace may connect more than one account.
5. Confirm the connection is active.

Connections belong to the workspace, not to one conversation. Disconnecting one prevents workflows that reference it from completing successfully.

Build a workflow

1. Open Settings → Automations and create a workflow.
2. Start from a template, describe a workflow for AI drafting when available, or open the builder directly.
3. Choose a trigger.
4. Add conditions that narrow when it should run.
5. Add one or more action steps and any branches.
6. Test the trigger and conditions against recent matching messages when that option is available.
7. Name, save, and enable the workflow.

Choose a trigger

Conversation triggers include new inbound messages, completed AI triage, status or label changes, assignment changes, outbound sends, unanswered conversations, and time spent in a status.

Task triggers include creation, edits, status changes, assignee or label changes, comments, due or overdue times, and archive events.

Automations do not re-trigger themselves for the same automated change, which prevents simple workflow loops.

Choose actions

Depending on the trigger, steps can:

• Set conversation status, labels, priority, category, assignees, snooze time, archive state, or internal notes.
• Create or update tasks, assignees, labels, due dates, comments, and archive state.
• Send an automatic email reply.
• Post to Slack.
• Create a Trello card.
• Save attachments to Dropbox.
• POST to a webhook.

Webhook URLs must use HTTPS, must not contain credentials, and must resolve to a public host. Private-network and local addresses are rejected.

Review run history

Use workflow run history to confirm which trigger matched, which conditions passed, and where a step failed. Provider errors often require reconnecting the external account, inviting the Repliqo Slack app to a private channel, or selecting a destination the connection can access.

Disable a workflow while diagnosing unexpected matches. Editing a workflow changes future runs; it does not roll back actions already completed.

Success looks like

• The workflow has one clear trigger and conditions narrow enough to be safe.
• Every external step references an active workspace connection.
• Tests match the intended recent messages and exclude obvious non-matches.
• Run history shows successful steps without repeated provider errors.

Common problems

• No recent test matches: simplify the condition and confirm the trigger has recent eligible events.
• Slack channel is missing: ensure the app can access the channel; private channels may require /invite @Repliqo.
• Trello board or list is missing: reconnect the account or confirm the authorized user has access.
• Dropbox upload fails: reconnect the referenced Dropbox account and verify the message contains attachments.
• Webhook is rejected: use a public HTTPS endpoint without embedded username or password credentials.

Next steps

• Organize conversation work.
• Automate task workflows.
• Use MCP for agent-driven workflows.