---
id: "fluxos.automacoes-externas"
titulo: "Automations from external hosts"
resumo: "See scheduled jobs that belong to another system, without confusing them with Elyra's routines."
idioma: "en"
tipo: "guia"
categoria: "quadro"
aplicavelDesde: "0.0.16"
capabilities: ["automation.external.hosts"]
estadoEditorial: "aprovado"
nivelEvidencia: "artefato-distribuido"
refFonte: "27574c339b58316408f6be2d62169d59041d07bf"
revisaoFonte: "2026-09-24"
revisor: "mantenedor (v1, 2026-10-03)"
rota: "/docs/en/fluxos/automacoes-externas/"
fonte: "pt-br/fluxos/automacoes-externas.md"
caminhoPublico: "docs/publica/en/fluxos/automacoes-externas.md"
hashFonte: "sha256:555899c607d41e0f6a64b5682cbf480eb1861b702d6b18e3279b12e3aed67ac0"
hashDestaPagina: "sha256:9fd095b57af4bcfa13934b3f9a12104419ac0f75ac732ef7c31059b1befa3e93"
traducaoAssistidaPorIA: true
traducaoDesatualizada: false
corpoRetido: false
---
<!-- traducao-assistida-por-ia: idioma=EN fonte=pt-br/fluxos/automacoes-externas.md fonteHash=sha256:555899c607d41e0f6a64b5682cbf480eb1861b702d6b18e3279b12e3aed67ac0 estado=atual -->

The **Automations** screen has two groups. The first, **Your routines**, is Elyra's. The second, **External
hosts**, shows jobs that **are not Elyra's** — they belong to another system, and the app merely presents
them.

## What the section shows

It only appears when there is an external host configured; with none, the group does not exist on the
screen. When it exists, each host reports which **state** it is in:

| State | What it means |
|---|---|
| **Manageable** | The app can query and trigger that host's jobs |
| **Read-only** | The app shows the jobs, but cannot change them |
| **Unavailable** | The host did not respond; what appears may be out of date |

Each job brings the schedule, the run history and what it asks for.

## What is Elyra's and what is not

This is the distinction that avoids confusion:

- **The schedule, execution, editing and history of an external job belong to that host's provider.** What
  the app does is a request; the other system decides.
- **There is no equivalent command in Elyra's command line** to create or edit these automations.
- **Availability depends on the host.** An external job may be visible today and unavailable tomorrow,
  without anything having changed in Elyra.
- **There is no promise of synchronization.** What you see is what the host reported on the last query.

## When to use this section

- To **know what already runs** in another system before creating a similar routine in Elyra.
- To **trigger** an external job, when the host allows it.
- To **see the history** of something that already exists, without switching tools.

## Scope and limits

- **Do not assume the action will work.** A read-only host refuses the change; an unavailable host receives
  nothing.
- **The reading may be stale.** Without a response from the host, what is on the screen is the last known
  state.
- **States and host names are not guaranteed across releases** — they depend on what each external provider
  exposes.

## See also

- [Scheduled automations](/docs/en/fluxos/automacoes/)
- [Agent notifications](/docs/en/fluxos/notificacoes/)