in other news I installed @n8n_io tonight and holy moly it’s good
it’s compatible with EVERYTHING
Back to Integrations
Integrate Execute Workflow with 500+ apps and services
n8n lets you connect Execute Workflow with hundreds of other apps. Create sophisticated automations between Execute Workflow and your stack.
Popular ways to use Execute Workflow integration
Execute another workflow
Companion workflow for Execute Workflow node docs
amudhan
+5
Gmail campaign sender: Bulk-send emails and follow up automatically if no reply
This workflow allows you to send multi-step email campaigns using n8n, Gmail and Google Sheets.
You define a sequence of emails, and a list of email addresses to send them to. The first email is sent to everyone, but the later emails in the sequence are only sent if no-one has replied to the thread yet.
This means you only need to worry about replying to people who respond to your email, not chasing people who don’t.
Requirements
A list of emails in a Google sheet. You can define extra info that will be available to your email templates (e.g. name, company, etc.)
A sequence of emails to send, plus how long to wait to send each one, e.g.
On day 0:** “Hi, {name} — nice to meet you at the conference. Was wondering whether {company} would be interested in a quick call about X?”
On day 3:** “Hi, {name}, just wanted to check in on this. Let me know if there’s any interest!”
On day 7:** “{name}, just wanted to give this one last try”
A Gmail account (although you could also swap out that part for any other email service)
How it works
When sending the emails, n8n inserts a hidden attribute in each one that tags it as being part of the email campaign. It then regularly looks through the email threads with that tag and checks whether:
No-one has replied yet
It’s time to send the next message
The workflow doesn’t send emails on weekends.
Notes
This workflow is not intended for spam! Please use responsibly
You can use this workflow for multiple different campaigns by making copies of the workflow and changing the sequence / Google Sheet that it uses
David Roberts
+5
Standup bot (4/4): Worker
This is the fourth workflow for the Mattermost Standup Bot. This workflow sends the team a message every morning to ask them three standup questions.
What have you accomplished since your last report?
What do you want to accomplish until your next report?
Is anything blocking your progress?
Once answered, the answers are sent to a Mattermost channel.
The "Read Config" nodes will need to be updated to point to the ID of the "Standup Bot - Read Config" workflow and the "Override Config" node will need to point to "Standup Bot - Override Config"
Jonathan
+7
🤖 Advanced Slackbot with n8n
Use case
Slackbots are super powerful. At n8n, we have been using them to get a lot done.. But it can become hard to manage and maintain many different operations that a workflow can do.
This is the base workflow we use for our most powerful internal Slackbots. They handle a lot from running e2e tests for Github branch to deleting a user. By splitting the workflow into many subworkflows, we are able to handle each command seperately, making it easier to debug as well as support new usecases.
In this template, you can find eveything to setup your own Slackbot (and I made it simple, there's only one node to configure 😉). After that, you need to build your commands directly.
This bot can create a new thread on an alerts channel and respond there.
Or reply directly to the user.
It responds for help request to return a help page.
It automatically handles unknown commands.
It also supports flags and environment variables. For example /cloudbot-test info mutasem --full-info -e env=prod would give you the following info, when calling subworkflow.
How to setup
Add Slack command and point it up to the webhook. For example.
Add the following to the Set config node
alerts_channel with alerts channel to start threads on
instance_url with this instance url to make it easy to debug
slack_token with slack bot token to validate request
slack_secret_signature with slack secret signature to validate request
help_docs_url with help url to help users understand the commands
Build other workflows to call and add them to commands in Set Config. Each command must be mapped to a workflow id with an Execute Workflow Trigger node
Activate workflow 🚀
How to adjust
Add your own commands.
Depending on your need, you might need to lock down who can call this.
Mutasem
+4
Retrieve a Monday.com row and all data in a single node
This workflow is a building block designed to be called from other workflows via an Execute workflow node. When called from another workflow, and given the JSON input of a "pulse" field with the ID to pull from monday, this workflow will return:
The items name and ID
All column data, indexable by the column name
All column data, indexable by the column's ID string
All board relation columns, with their data and column values
All subitems, with their data and column values
For example:
++Prerequisites++
A monday.com account and credential
A workflow that needs to get detailed data from a monday.com row
The pulse id of the monday.com row to retreive data from.
++Setup++
Import the workflow
Configure all monday nodes with your credentials and save the workflow
Copy the workflow ID from it's URL
In a different workflow, add an Edit Fields node, to output the field "pulse", with the monday item you want to retrieve.
Feed the Edit Fields node with your pulse into an Execute workflow node, and paste the workflow ID from above into it
This "pulse" field will tell the workflow what pulse to retreive. This can be populated by an expression in your workflow
There is an example of the Edit Fields and Execute Workflow nodes in the template
Joey D’Anna
+3
Prevent simultaneous workflow executions with Redis
Purpose
This ensures that executions of scheduled workflows do not overlap when they take longer than expected.
How it works
This is a separate workflow which monitors the execution of the main workflow
Stores a flag in Redis (key dynamically named after workflow ID) which indicates if the main workflow is running or idle
Only calls the main workflow if the last execution has finished
Setup
Update the credentials suitable for your Redis instance
Replace the Schedule Trigger of your main workflow by an Execute Workflow Trigger
Copy the workflow ID from the URL
Paste the workflow ID in the Execute Workflow Node of this workflow
Configure the Schedule Trigger Node
Mario
Load More Workflows
Documents
Execute Workflow Node Docs + Examples
Over 3000 companies switch to n8n every single week
Connect Execute Workflow with your company’s tech stack and create automation workflows
aaron
@acar321
qupaya technologies
@qupaya
We're using the @n8n_io cloud for our internal automation tasks since the beta started. It's awesome! Also, support is super fast and always helpful. 🤗
Cris
Last week I automated much of the back office work for a small design studio in less than 8hrs and I am still mind-blown about it.
n8n is a game-changer and should be known by all SMBs and even enterprise companies.
