Request: Native n8n Node or Integration for Concourse CI

[ma9ni]

Request: Native n8n Node or Integration for Concourse CI

Hi Concourse team 👋,

First of all, thank you for maintaining such a powerful CI/CD platform — I’ve been using Concourse CI extensively for my automation pipelines, and it’s been rock solid.

While building workflows that combine Concourse CI with other tools, I’ve noticed there is no native node or integration for Concourse in n8n (the open-source automation tool similar to Zapier).
This makes it harder to connect Concourse events and jobs with broader automation (notifications, reporting, integrations with other APIs, etc.).

---

Feature Request / Questions

• Is there any plan or discussion about adding native support for Concourse CI in n8n?
• If not, would you consider collaborating with the n8n community to enable this (even basic actions like triggering pipelines, fetching build status, etc.)?

---

Why This Matters

Adding this integration would unlock great possibilities for teams using both tools:

• Trigger Concourse pipelines based on external events (e.g., GitHub, Slack, custom APIs)
• Automatically fetch build logs or statuses for reporting dashboards
• Connect Concourse pipelines with notification systems seamlessly

---

Alternatives Today

Currently, the only workaround is using the HTTP Request node in n8n to call Concourse’s API manually, but this is less user-friendly compared to dedicated nodes.

---

Would love to hear your thoughts — is this something you’d be open to, or are there recommended patterns already in use for integrating Concourse with external automation tools like n8n?

Thanks!

[taylorsilva]

I think this is the first time someone has mentioned n8n here.

When it comes to external integrations, the default answer is to build your own resource type that connects Concourse to whatever external service you want to integrate with: https://concourse-ci.org/implementing-resource-types.html

You can try using webhook tokens, though I admit they are limited in functionality: https://concourse-ci.org/resources.html#schema.resource.webhook_token

We're very careful about what we nativley support within the concourse binary. The only external services we connect and support to are related to:

• secrets management (Vault, AWS Secrets manager, etc.)
• metrics (Datadog, Prometheus, etc.)
• Authentication (via dex, and only subset of connectors)