Reference · Nodes
Development integrations and nodes
Development nodes connect workflows to the tools engineering teams already run: source control with GitHub, GitLab and Git, builds with Jenkins, CircleCI and Travis CI, deploys with Netlify and AWS Lambda, servers through SSH and Execute Command, and error tracking with Sentry.io. Every trigger in this category is a webhook, so a push, a merged pull request, a finished test run or a deploy starts a workflow as it happens.
39 nodes — 27 actions and 12 triggers. Every page documents the shipped node: real parameters, real outputs, real error behaviour.
Source control, builds, deploys and servers
Source control. GitHub and GitLab manage files, issues, releases and repositories through their APIs; GitHub can also dispatch an Actions workflow. Git clones, commits and pushes repositories inside the workflow’s workspace.
Builds and tests. Jenkins triggers builds and manages jobs, CircleCI triggers and lists pipelines, and Travis CI triggers, cancels and restarts builds.
Deploys and infrastructure. Netlify manages sites and deploys, AWS Lambda invokes functions, and Cloudflare manages origin-pull certificates. UptimeRobot manages uptime monitors and status pages.
Servers and commands. SSH runs commands and transfers files on a remote host, FTP moves files over FTP or SFTP, and Execute Command runs a shell command and captures its output and files.
Messaging and security. Kafka and RabbitMQ publish messages. Sentry.io manages issues and releases, MISP manages threat-intelligence events, and urlscan.io scans URLs.
Triggers
All webhook triggers: GitHub Trigger, GitLab Trigger, Bitbucket Trigger, Netlify Trigger, Currents Trigger, Linear Trigger, Taiga Trigger, Figma Trigger, Webflow Trigger, TheHive Trigger, TheHive 5 Trigger and Venafi TLS Protect Cloud Trigger.
Example workflows
- Tag to release. GitLab Trigger fires when a new tag is pushed, Jenkins triggers a parameterized build, and Sentry.io creates a release with the commit information.
- Review on push. GitHub Trigger starts the run when code is pushed, GitHub downloads the changed file, OpenAI Reasoning analyzes the code for bugs, and GitHub creates an issue with the findings.
- Check a suspicious link. urlscan.io scans a URL and returns its security verdicts, If branches on the verdict, and MISP adds an attribute to a threat-intelligence event.
Actions
Triggers
Nodes that START a workflow when something happens.
Frequently asked questions
Which development events can start a workflow?
GitHub Trigger, GitLab Trigger and Bitbucket Trigger fire on repository events such as pushes, pull or merge requests and issues. Netlify Trigger covers deploys and form submissions, and Currents Trigger covers CI test runs. Linear Trigger and Taiga Trigger cover issue tracking, Figma Trigger design files, Webflow Trigger site events, TheHive Trigger and TheHive 5 Trigger security alerts and cases, and Venafi TLS Protect Cloud Trigger certificate events.
Can a workflow run my own scripts and commands?
Yes. Execute Command runs a shell command in an isolated execution directory and can write upstream binary data to disk first, so command-line tools such as ImageMagick or ffmpeg can work on real files. SSH runs commands on a remote server you control, and the Code node in Core Nodes runs JavaScript or Python inside the workflow. User-supplied code runs sandboxed.
How do development nodes combine with AI nodes?
An AI node can read what a development tool reports and write something back. Sentry.io lists the unresolved issues in a project, Claude Chat summarizes them, and GitHub opens an issue with the summary so the work is tracked where the team already looks.
Last reviewed . Spotted something wrong? Tell us.