Integrations: where Echelar listens, and where it answers.

Work enters from the tools your company already uses and returns to the same place. Each integration is installed on purpose, scoped to what you enroll, and explicit about what it cannot do.

Slack app

Call Echelar from the channel where the work already is.

Mention Echelar in an enrolled channel. The answer, the diagnosis, or the pull request comes back to the thread.

See how Slack connectsGitHub App

Every job ends in GitHub, as a pull request.

Review after CI, fixes you start with a label, and the pull request every other job returns.

See how GitHub connectsLinear integration

Assign the issue to Echelar. The pull request comes back on it.

Assign an issue to Echelar. Progress streams onto the issue and the pull request attaches to it. The board moves only if you say so.

See how Linear connectsAutomations on a schedule

Put recurring work on a schedule. Review what comes back.

Describe the chore once. Echelar drafts the schedule; a person enables it; code changes come back as pull requests.

See how Schedules connects