Book a call Get in touch

Productivity & Collaboration

Articles, blogs, guides and how-tos about business process automation.

  • n8n

    n8n

    The n8n node is a management and utility node within n8n itself. It lets you interact with your n8n instance programmatically from inside a workflow: list workflows, get workflow details, activate or deactivate workflows, and retrieve execution data. This turns n8n into a self-managing platform where workflows can monitor and control other workflows. This node is useful for operational management of n8n at scale. When you have dozens or hundreds of workflows running, you need visibility into which ones are active, which have failed recently, and which need attention. Instead of manually checking the n8n dashboard, you can build a monitoring workflow that uses the n8n node to pull execution logs, check for failures, and send alerts to Slack or email. The node can also automate workflow lifecycle management. You can build workflows that activate seasonal automations on a schedule, deactivate workflows during maintenance windows, or generate reports on workflow execution counts and success rates. For teams that manage n8n for multiple clients or departments, this provides centralised control. At Osher, we use the n8n node in every client deployment for operational monitoring. Our n8n consulting team builds monitoring dashboards and alerting workflows that report on workflow health, execution failures, and performance metrics. When we manage n8n for clients through our business automation services, this node is how we keep tabs on everything running across the platform.
    n8n consultants
  • Jira Software

    Jira Software

    Jira Software is Atlassian’s project management and issue tracking platform, built primarily for software development teams but used widely across IT, operations, and business teams. It provides Scrum boards, Kanban boards, sprint planning, backlog management, and detailed reporting — all structured around the concept of issues (tasks, bugs, stories, epics) that move through configurable workflows. The problem Jira solves is visibility. When development and IT teams track work across spreadsheets, emails, or chat messages, things get lost. Jira centralises all work items with status tracking, assignees, priorities, due dates, and links to related code commits or pull requests. Managers get dashboards and burndown charts; team members get a clear queue of what to work on next. For automation, Jira’s REST API is comprehensive. The n8n Jira node supports creating issues, updating fields, adding comments, transitioning statuses, and reading issue data. This means you can build workflows that automatically create Jira tickets from form submissions, escalate support tickets from a helpdesk into engineering sprints, or sync project status with external reporting tools. Osher connects Jira into broader system integration projects where development teams need their project management data flowing into other business systems. We also build process automation workflows that eliminate manual ticket creation and status updates.
    Jira Software consultants
  • Trello

    Trello

    Trello is a visual project management tool from Atlassian that organises work using boards, lists, and cards. Each board represents a project or process, lists represent stages (like “To Do”, “In Progress”, “Done”), and cards represent individual tasks that move between lists as work progresses. It is deliberately simpler than tools like Jira, which makes it popular with non-technical teams managing marketing campaigns, content calendars, onboarding checklists, and operational workflows. The problem Trello solves is coordination. When a team tracks tasks across email threads, spreadsheets, and chat messages, things fall through the cracks. Trello gives everyone a shared, visual view of what needs doing, who is doing it, and what stage it is at. Cards can hold checklists, attachments, due dates, labels, and comments — enough structure to track work without the overhead of a full project management suite. For automation, Trello’s REST API lets you create, update, move, and archive cards programmatically. The n8n Trello node supports these operations, so you can build workflows that create cards from form submissions, move cards between lists when external events occur, or sync Trello boards with CRM and helpdesk systems. Osher connects Trello into business automation workflows for teams that need a lightweight task management layer. We also use it in system integration projects where Trello boards need to stay in sync with other platforms like Slack, Google Sheets, or a CRM.
    Trello consultants
  • Notion Trigger

    Notion Trigger

    The Notion Trigger node in n8n starts a workflow automatically whenever something changes in a Notion workspace. It polls your Notion database or page at regular intervals and fires when it detects new or updated entries. This turns Notion from a static workspace into an active part of your automation stack. Many teams use Notion as their central hub for project tracking, content calendars, meeting notes, and task management. The problem is that updates in Notion rarely flow to other tools automatically. When a project status changes, someone has to manually update the CRM, notify the team on Slack, or create a task in the project management tool. Notion Trigger eliminates that manual step. The node connects through Notion’s API using an internal integration token. You configure it to watch a specific database and trigger when pages are created or updated. It returns the page properties (title, status, dates, people, select fields) as JSON, which you can then route to any other node in your workflow. At Osher, we connect Notion to other business tools for teams that have outgrown manual processes. A common build is Notion-to-Slack notifications when project statuses change, or Notion-to-CRM syncs that keep sales pipelines updated. Our business automation team can set this up so your Notion workspace drives action across your entire tool stack.
    Notion Trigger consultants

  • Execute Workflow Trigger

    The Execute Workflow Trigger node is an n8n trigger that lets one workflow call another as a sub-workflow. It acts as the entry point for a workflow that is designed to be invoked by a parent workflow using the Execute Workflow node, rather than running on its own schedule or webhook. As your n8n automations grow, individual workflows can become long and difficult to maintain. The Execute Workflow Trigger solves this by allowing you to break large workflows into smaller, reusable modules. A parent workflow handles the main logic and calls sub-workflows for specific tasks, passing data in and receiving results back. This is the same concept as functions in programming. You build a sub-workflow once (for example, “look up a customer in the CRM and return their details”) and call it from any parent workflow that needs that data. The Execute Workflow Trigger node sits at the start of the sub-workflow and receives the input data from the parent. At Osher, we use this pattern extensively in complex automation projects. Our n8n consultants design modular workflow architectures where shared logic lives in sub-workflows. This keeps each workflow focused, testable, and maintainable. If you are building more than a handful of n8n workflows, our business automation team can help you structure them properly with sub-workflow patterns.
    Execute Workflow Trigger consultants
  • Google Calendar

    Google Calendar

    The Google Calendar node in n8n connects to the Google Calendar API via OAuth2 and lets your workflows create, read, update, and delete calendar events programmatically. It supports setting event details including title, description, start and end times, attendees, location, reminders, recurrence rules, and colour coding. The node also has a trigger mode that fires a workflow when a calendar event starts, ends, or is created. Scheduling is tightly linked to operational processes: client meetings trigger preparation tasks, appointment bookings need confirmation emails, and team availability affects project timelines. The Google Calendar node connects these scheduling events to the rest of your business systems so that calendar activity drives automatic actions rather than relying on someone to remember the next step. At Osher, we integrate Google Calendar into business automation workflows where scheduling events need to trigger or feed data to other systems. We’ve built workflows where new calendar bookings automatically create client records, send preparation checklists to team members, update project timelines, and trigger follow-up sequences after meetings conclude. Our n8n consulting team connects Calendar to CRMs, project management tools, and communication platforms.
    Google Calendar consultants
  • Notion

    Notion

    The Notion node in n8n connects your workflows to the Notion API, letting you create, read, update, and search pages and database entries in your Notion workspace. It authenticates using Notion’s internal integration tokens and supports operations across databases, pages, blocks, and users, making it possible to automate content management, project tracking, and knowledge base maintenance entirely from n8n. Notion is widely used as a project management tool, wiki, CRM, content calendar, and task tracker. The problem is that keeping Notion data in sync with your other business systems usually involves manual copy-paste or constant context switching. The Notion node in n8n eliminates that by connecting Notion to your databases, APIs, communication tools, and other applications automatically. At Osher, we build Notion integrations for clients who use it as a central workspace. Common automations include: creating new Notion database entries when leads come in from web forms, updating project status pages automatically from data in other project tools, syncing CRM data between Notion databases and external systems, building content publishing pipelines where drafts in Notion trigger review and publishing workflows, and feeding task completions from Notion into reporting dashboards. These automation workflows keep Notion accurate without anyone needing to update it manually. The node supports creating and querying database items with filters and sorts, appending blocks to pages, retrieving page content, and searching across your workspace. Our integration team can connect Notion with any system in your stack.
    Notion consultants

  • RSS Read

    The RSS Read node in n8n pulls structured data from any RSS or Atom feed URL and outputs it as individual items for downstream processing. Each item includes the title, link, publication date, description, author, and content fields from the feed. This makes it a practical starting point for workflows that need to react to new blog posts, news articles, product updates, or changelog entries from external sources. Businesses use RSS Read to solve a common problem: keeping track of information published across dozens of websites without manually checking each one. A marketing team might monitor competitor blogs for new content. An operations team might track regulatory updates from government sites. A product team might watch release notes from tools in their stack. RSS Read pulls that information automatically and passes it to other n8n nodes for filtering, formatting, storage, or notification. At Osher, we build system integrations that connect RSS Read with Slack channels, Airtable bases, email alerts, and CRM records. We’ve used it in content monitoring pipelines, competitive intelligence dashboards, and automated reporting workflows. If you need structured data from public web sources feeding into your business systems, our n8n consulting team can set that up.
    RSS Read consultants
  • Gmail

    Gmail

    The Gmail node in n8n connects directly to the Gmail API using OAuth2 authentication, giving your workflows full programmatic access to send, read, reply to, label, and organise emails. Unlike generic SMTP/IMAP connections, the Gmail node works with Gmail-specific features such as labels, threads, and the Gmail search syntax (e.g., from:[email protected] has:attachment after:2026/01/01). This matters for businesses because email is still where most client communication, invoices, approvals, and notifications land. The Gmail node lets you pull specific emails into an n8n workflow, extract data from them, and pass that data to CRMs, databases, project management tools, or accounting systems without anyone manually copying and pasting. It also works in the other direction: your workflows can send formatted emails, reply within existing threads, add labels, and move messages to specific folders. At Osher, we use the Gmail node in client projects ranging from sales automation (auto-logging inbound enquiries to a CRM) to automated data processing (extracting invoice details from email attachments). We built a similar email-driven workflow for a healthcare client automating patient data entry. If email is a bottleneck in your operations, our n8n team can automate it.
    Gmail consultants

  • Email Trigger (IMAP)

    The Email Trigger (IMAP) node in n8n monitors any IMAP-compatible email inbox and fires a workflow whenever a new message arrives. Unlike the Gmail-specific trigger, this node works with any email provider that supports IMAP, including Outlook, Yahoo, Zoho, FastMail, and self-hosted mail servers. It connects using standard IMAP credentials (host, port, username, password) and polls the inbox at a configurable interval. This is useful for businesses that receive operational emails through non-Google email systems, or that need to monitor shared inboxes, vendor notification addresses, or legacy email accounts. The trigger passes the full email data into your workflow: sender, recipients, subject, body (plain text and HTML), headers, and attachments. From there, other n8n nodes can parse the content, extract data, and route it to the right system. At Osher, we use the IMAP trigger in business automation projects where clients rely on Outlook or self-hosted email. We’ve built workflows that automatically create support tickets from incoming emails, extract invoice data from attachments, and route client requests to the correct team based on subject line keywords. Our n8n consulting team can connect any IMAP mailbox to your operational workflows.
    Email Trigger (IMAP) consultants
  • Airtable

    Airtable

    The Airtable node in n8n connects to the Airtable API to read, create, update, and delete records in your Airtable bases. It authenticates via personal access token or OAuth2 and gives your workflows direct access to any base, table, and view you have permissions for. You can search records using Airtable’s formula syntax, retrieve linked records across tables, and handle file attachments stored in Airtable fields. Airtable sits in a sweet spot between spreadsheets and full databases. Many businesses use it as their operational backbone for project tracking, client management, inventory, and content calendars. The problem is that data entered in Airtable often needs to reach other systems: CRMs, invoicing tools, email marketing platforms, or reporting dashboards. The n8n Airtable node solves this by making Airtable a live, connected part of your automation stack rather than an isolated spreadsheet. At Osher, Airtable is one of the most common tools in our client projects. We built a talent marketplace integration where Airtable served as the central record store connected to multiple automated pipelines. Our system integration team regularly connects Airtable with tools like Slack, Google Sheets, Xero, and custom APIs to keep business data synchronised across platforms.
    Airtable consultants
  • Google Drive

    Google Drive

    The Google Drive node in n8n connects to the Google Drive API via OAuth2 and lets your workflows create, read, update, delete, move, copy, and share files and folders programmatically. It supports operations on Google Docs, Sheets, Slides, and any file type stored in Drive. You can search for files using Drive’s query syntax, manage sharing permissions, and download or upload file content as binary data for processing by other nodes. Most businesses already store documents in Google Drive, but the files sit there passively. Staff manually upload reports, share folders by hand, and download attachments to reprocess them elsewhere. The Google Drive node turns Drive into an active part of your workflow: incoming documents get automatically filed, generated reports get saved to the right folder with the right permissions, and files that arrive in one system get mirrored to Drive for team access. At Osher, we connect Google Drive into client workflows as part of our automated data processing work. A common pattern is receiving documents via email or webhook, processing them through an AI extraction step, and saving both the original and extracted data to organised Drive folders. We also built document pipelines similar to our medical document classification project, where files are automatically categorised and routed. Our n8n consultants can connect Drive to any part of your operational workflow.
    Google Drive consultants
  • GitHub

    GitHub

    The GitHub node in n8n connects to the GitHub REST and webhook APIs using personal access tokens or OAuth2 authentication. It lets your workflows interact with repositories, issues, pull requests, releases, and users programmatically. You can create and update issues, trigger workflows on push or PR events via webhooks, read repository contents, manage labels, and post comments, all from within an n8n automation. Development teams already live in GitHub, but the operational work around code, including issue triage, release notifications, deployment tracking, and cross-team communication, still involves manual steps. The GitHub node closes that gap by connecting your code repository to the rest of your business tools. When a PR gets merged, Slack gets notified. When an issue is labelled as urgent, it gets pushed to your project management board. When a release is published, clients get an update email. At Osher, we use the GitHub node in system integration projects where development activity needs to flow into project management, client communication, or deployment pipelines. We also use it in our own internal tooling, connecting our repositories to Slack alerts and task tracking. Our custom development team can build GitHub-connected workflows for any DevOps or project management use case.
    GitHub consultants

  • SSH

    The SSH node in n8n executes commands on remote servers over an encrypted SSH connection. You configure it with a hostname, port, and authentication credentials (password or private key), and it runs shell commands on the target machine and returns the stdout and stderr output to your workflow. This gives n8n the ability to interact with any Linux or Unix server as part of an automated pipeline. This matters when your automation needs to touch infrastructure directly. Restarting a service, pulling fresh data from a server-side script, checking disk usage, deploying a configuration change, or running a database backup command are all tasks that require shell access. The SSH node lets you include these steps in a broader workflow without writing a separate script or logging into the server manually. At Osher, we use the SSH node in system integration projects where part of the workflow involves interacting with on-premise servers or VPS instances. For example, triggering a data export script on a client’s server, pulling log files for analysis, or restarting services as part of an automated deployment pipeline. Our n8n consulting team builds these workflows with proper key-based authentication and scoped command permissions.
    SSH consultants
  • Slack

    Slack

    The Slack node in n8n connects your workflows directly to the Slack API, allowing you to send messages, create channels, upload files, manage users, and react to events inside Slack workspaces. It supports both OAuth2 authentication and webhook-based integration, giving you full programmatic access to Slack from within your automations. Slack is where most teams already live during the workday, which makes it the ideal destination for automated notifications, alerts, and reports. Instead of switching between apps to check on the status of orders, deployments, support tickets, or workflow errors, your team gets updates delivered to the channels they already monitor. At Osher, Slack integration is part of almost every automation project we deliver. We build workflows that post structured alerts when n8n workflows fail, send daily sales summaries pulled from CRM data, notify support teams when high-priority tickets arrive, and deliver formatted reports from database queries directly into Slack channels. We also build interactive Slack workflows using Block Kit messages with buttons that trigger follow-up actions in n8n. The n8n Slack node supports operations across messages, channels, files, reactions, stars, and user groups. Combined with the Slack Trigger node (which listens for events in Slack and starts workflows), you can build full two-way automations between Slack and any other system in your stack. Talk to our integration team about connecting Slack to your business systems.
    Slack consultants

  • Spreadsheet File

    The Spreadsheet File node in n8n reads and writes spreadsheet files in CSV, XLSX (Excel), and ODS (OpenDocument) formats. It converts spreadsheet data into JSON rows that other n8n nodes can process, and converts JSON data back into downloadable spreadsheet files. This is the node you reach for whenever your workflow needs to import data from a spreadsheet or export data as one. Most businesses still rely heavily on spreadsheets for reporting, data imports, and information sharing. The Spreadsheet File node bridges the gap between those spreadsheet-based processes and your automated workflows. Instead of someone manually opening a CSV, copying rows into another system, and reformatting the output, an n8n workflow can handle the entire process untouched. At Osher, we use this node in data processing automations regularly. Common builds include: importing client-uploaded CSV files into databases, generating formatted XLSX reports from API data for stakeholders, converting between CSV and Excel formats during system migrations, and processing bulk data updates from spreadsheet uploads. We pair the Spreadsheet File node with the Convert to/from Binary Data node to handle the file transfer portion of these workflows. If your team spends time manually importing or exporting spreadsheet data between systems, that process can almost certainly be automated. Contact our automation team to discuss replacing manual spreadsheet handling with reliable, repeatable workflows.
    Spreadsheet File consultants
  • Discord

    Discord

    The Discord node in n8n connects your workflows to the Discord API, letting you send messages, manage channels, handle server members, and interact with Discord communities programmatically. It supports both bot token authentication and webhook-based messaging, covering a wide range of Discord operations from simple notifications to full server management. Discord has grown well beyond gaming into a platform used by businesses, developer communities, crypto projects, SaaS companies, and education providers for community engagement and team communication. Automating Discord interactions means your community stays informed and active without someone manually posting updates around the clock. At Osher, we build Discord automations for clients who manage active communities or use Discord internally for team communication. Common implementations include: posting automated announcements when new content is published, sending alert messages when systems go down or errors occur, syncing Discord activity data with CRM or analytics tools, and building bot workflows that respond to user commands with data pulled from APIs or databases. These automation workflows keep communities engaged without consuming staff time. The n8n Discord node handles sending messages (with embeds and attachments), managing channels and roles, retrieving member lists, and executing server management operations. Combined with Discord webhook triggers, you can build interactive bots that respond to community activity in real time. Contact our integration team to connect Discord with your business systems.
    Discord consultants

  • Execute Workflow

    The Execute Workflow node in n8n calls another workflow from within the current one, essentially creating sub-workflows. This lets you break complex automations into smaller, reusable components instead of building one massive workflow that is difficult to understand, test, and maintain. The concept is similar to calling a function in programming. Your main workflow reaches the Execute Workflow node, passes data to the sub-workflow, waits for it to finish, and receives the sub-workflow’s output data back. The sub-workflow runs independently with its own nodes and logic, and can be reused by multiple parent workflows. This is important for keeping automation projects manageable. A workflow that processes orders might need to validate addresses, check inventory, calculate shipping, and update the CRM. Instead of cramming all of that into a single workflow with dozens of nodes, you build each step as a separate workflow and call them in sequence using Execute Workflow nodes. If your address validation logic changes, you update one sub-workflow, and every parent workflow that calls it gets the update automatically. At Osher, we use Execute Workflow extensively in our AI agent and business automation projects. Complex agents often call sub-workflows for specific tasks like document retrieval, database lookups, or API calls. Our n8n consulting team designs modular workflow architectures from the start so that individual components can be tested, updated, and reused independently.
    Execute Workflow consultants
  • Telegram

    Telegram

    Telegram is a cloud-based messaging platform with a powerful Bot API that makes it one of the easiest messaging services to integrate into automated workflows. The Telegram node in n8n connects your workflows to Telegram bots, letting you send messages, photos, documents, and location data to individual users, groups, or channels programmatically. The node supports both sending and receiving. As a trigger, it listens for incoming messages to your Telegram bot and starts a workflow when someone sends a command or message. As an action node, it sends messages, files, or media from your workflow to specified Telegram chats. This two-way communication makes Telegram a practical interface for interacting with automations on the go. Common uses include sending real-time alerts when workflows complete or fail, building conversational interfaces for internal tools (e.g., a bot that lets staff check stock levels by typing a product code), and pushing notifications from monitoring systems to a team channel. Telegram’s generous API limits and free bot creation make it a cost-effective alternative to SMS for automated notifications. At Osher, we integrate Telegram into business automation and AI agent projects where teams need mobile access to their automation systems. We have built Telegram bots that serve as frontends for approval workflows, data lookup tools, and alert systems. Our n8n consulting team handles the full setup, from bot creation through to production deployment.
    Telegram consultants

  • Date & Time

    The Date & Time node in n8n converts, formats, and manipulates date and time values within your workflows. It handles the tedious but critical work of translating timestamps between different formats, time zones, and representations so that downstream systems receive dates in the exact format they expect. Date formatting issues are one of the most common causes of automation failures. One system stores dates as “2026-02-15”, another uses “15/02/2026”, and a third expects a Unix timestamp. An API returns times in UTC, but your reporting tool needs AEST. The Date & Time node handles all of these conversions without requiring custom JavaScript code. The node supports several operations: converting between date formats (ISO 8601, Unix timestamps, custom patterns), adding or subtracting time intervals (add 30 days for a due date, subtract 7 days for a lookback period), extracting components (get the month, day of week, or quarter from a date), and converting between time zones. You can chain multiple operations to handle complex date logic. At Osher, we use this node in every data processing workflow that involves dates, which is most of them. It is particularly important in our system integration projects where data flows between Australian and international systems with different date format conventions. Getting date handling right from the start prevents data corruption and reporting errors downstream.
    Date & Time consultants

  • Schedule Trigger

    The Schedule Trigger node in n8n starts a workflow at defined intervals, functioning like a cron job with a visual interface. Instead of setting up scheduled tasks on a server or relying on external schedulers, you configure the timing directly inside your n8n workflow, and it runs automatically on that schedule. The node supports flexible scheduling: every X minutes or hours, specific times of day, specific days of the week, and cron expressions for advanced patterns. You can configure it to run every weekday at 8:30am, every Monday at midnight, every 15 minutes during business hours, or on the first day of each month. All scheduling respects the time zone you configure, which matters when your server is in a different time zone to your business. Schedule Trigger is the starting node for any recurring automation. Daily report generation, hourly data syncs, weekly email digests, monthly invoice processing. If a task happens on a regular schedule and follows the same steps each time, it belongs in a Schedule Trigger workflow. At Osher, we use Schedule Trigger as the backbone of most RPA workflows and data processing pipelines we build for clients. A large portion of the automation projects we deliver start with “this needs to run every day at 6am” or “this report needs to go out every Friday afternoon”. Our n8n consulting team configures scheduling with proper time zone settings, error notification, and monitoring so you know your scheduled workflows are running reliably.
    Schedule Trigger consultants

  • Send Email

    The Send Email node in n8n sends emails directly from your workflows using an SMTP connection. Unlike email marketing platforms, this node sends transactional or operational emails as part of an automated process. Think order confirmations, report deliveries, alert notifications, and task assignments rather than marketing campaigns. The node connects to any SMTP server: Gmail, Outlook 365, Amazon SES, SendGrid, Mailgun, or your own mail server. You configure the SMTP credentials once, then use the node anywhere in your workflows to send emails with dynamic content pulled from the workflow data. Subject lines, body text, recipients, and attachments can all be populated from the data flowing through your automation. The node supports HTML email bodies, so you can send formatted messages with headings, tables, and links. It also handles file attachments, CC and BCC recipients, custom reply-to addresses, and plain-text fallback content. You can send to single recipients or loop through a list to send personalised emails to multiple people. At Osher, we use Send Email nodes in most business automation projects, usually for delivering reports, sending workflow completion summaries, and alerting team members when processes need attention. We also use it in sales automation workflows where leads receive personalised follow-ups based on their actions. Our n8n team configures SMTP settings for reliable delivery and sets up proper error handling so you know immediately if an email fails to send.
    Send Email consultants
  • Respond to Webhook

    Respond to Webhook

    The Respond to Webhook node in n8n lets you send a custom HTTP response back to the system that triggered a webhook-based workflow. By default, n8n’s Webhook trigger node sends a simple acknowledgement when it receives a request. The Respond to Webhook node replaces that with a response you control: custom status codes, headers, and body content. This matters when you are building APIs or integrations where the calling system expects specific data back. For example, a form submission on your website might trigger an n8n workflow that validates the data, checks a CRM, and then returns a personalised confirmation message. Without this node, the caller just gets a generic 200 OK with no useful payload. The node supports JSON, text, and binary response types. You can set response headers for CORS, content type, or caching. You can also return different responses based on workflow logic, sending a success message if validation passes and an error message if it fails. At Osher, we use this node extensively in our system integration projects and when building AI agent endpoints. It turns n8n into a proper API backend that external applications can call and receive structured data from, rather than just a one-way automation tool.
    Respond to Webhook consultants

  • Function Item

    The Function Item node in n8n runs custom JavaScript code on each item that passes through the workflow, one at a time. It is the single-item counterpart to the Function node (which processes all items at once), and it is ideal when you need to transform, reshape, or enrich individual data records. Where the built-in n8n nodes handle common tasks like HTTP requests and database queries, the Function Item node fills the gaps. Need to reformat a date string? Parse a nested JSON object? Calculate a value from multiple fields? Strip HTML tags from text? This node lets you write the exact JavaScript you need, applied to each item individually. The node receives each item as a JSON object, runs your code, and returns the modified item. You have access to standard JavaScript methods plus n8n’s built-in helper functions. You can add new fields, remove existing ones, or completely restructure the data shape before passing it to the next node. At Osher, we use Function Item nodes in nearly every data processing workflow we build. They are essential for cleaning up data from APIs that return inconsistent formats, mapping fields between systems with different schemas, and preparing data for downstream nodes that expect a specific structure. Our n8n consulting team writes clean, well-documented function code that future developers can maintain.
    Function Item consultants
  • Google Sheets

    Google Sheets

    Google Sheets is one of the most commonly used data sources in automation projects, and the Google Sheets node in n8n connects your spreadsheets directly into automated workflows. The node can read rows, append new rows, update existing rows, delete rows, and clear entire sheets, all without manual intervention. Many businesses run critical processes out of Google Sheets. Lead tracking, inventory counts, employee schedules, pricing tables, approval logs. The problem is that keeping these sheets in sync with other systems requires constant copying, pasting, and manual data entry. The n8n Google Sheets node eliminates that by reading from and writing to spreadsheets as part of a larger automated workflow. The node authenticates via OAuth2 or service account credentials and supports operations on any sheet within a spreadsheet. You can filter rows by column values, use header row mapping for structured data access, and handle large datasets with pagination. It works with both personal Google accounts and Google Workspace (business) accounts. At Osher, Google Sheets integration is part of nearly every business automation project we deliver. We have used it to build automated reporting dashboards, property inspection tracking systems, lead distribution workflows, and inventory sync pipelines. Our integration team connects Sheets to CRMs, accounting software, and custom databases so your data stays consistent across all platforms.
    Google Sheets consultants

  • Cron

    The Cron node (now called Schedule Trigger in newer n8n versions) triggers workflows on a time-based schedule. You configure it to fire at specific intervals (every 5 minutes, hourly, daily at 9am, weekly on Mondays, monthly on the 1st), and n8n automatically executes the workflow at those times. No manual triggering or external event is required. Scheduled execution is essential for automations that need to run on a recurring basis: pulling daily reports from an API, syncing data between systems every hour, sending weekly summary emails, running nightly data cleanup scripts, or checking for new records at regular intervals. The Cron node handles all of these timing patterns. The node uses standard cron expression syntax, giving you precise control over execution timing. You can set it to run at specific minutes, hours, days of the week, days of the month, and months. For simpler requirements, n8n also provides a visual interface where you select the interval without writing cron expressions directly. At Osher, the Cron node is the backbone of maintenance and reporting workflows we build for clients. Scheduled data syncs, automated report generation, and periodic health checks all rely on it. Our BOM weather data pipeline used scheduled triggers to pull fresh weather data at defined intervals. We use Cron-triggered workflows across data processing and RPA projects wherever tasks need to happen on a predictable schedule. If your business has recurring tasks that run on a timer, talk to our n8n team about automating them with scheduled workflows.
    Cron consultants

  • Switch

    The Switch node in n8n routes data items to different output branches based on the value of a field. While the If node handles binary yes/no decisions, the Switch node handles multi-way routing: send items down one of several paths depending on which value a field contains. Think of it as a multi-lane roundabout instead of a T-junction. A typical use case: incoming support tickets have a “category” field that could be “billing,” “technical,” “general,” or “urgent.” The Switch node reads that field and sends each ticket to the branch that handles its category. Billing tickets go to the finance workflow, technical tickets get escalated to engineering, general enquiries go to the standard response queue, and urgent tickets trigger an immediate alert. The Switch node supports matching on exact values, regex patterns, and numeric ranges. You configure up to four named outputs (or more in recent n8n versions), each with its own matching rules. Items that don’t match any rule go to a fallback output, so nothing gets silently dropped. It processes each item independently, so a batch of records can split across multiple output branches in a single execution. At Osher, we use the Switch node whenever a workflow needs to route data to more than two destinations. Our talent marketplace application processing used Switch nodes to route candidates to different evaluation pipelines based on role type. It’s a standard component in our business automation and RPA projects wherever multi-path routing is required. If your automation needs to sort items into multiple categories or route data to different systems based on type, talk to our n8n team about using the Switch node.
    Switch consultants

  • If

    The If node is n8n’s conditional branching tool. It evaluates a condition against incoming data and splits the workflow into two paths: one for items that match the condition (true) and one for items that don’t (false). This is how you add decision-making logic to an automation workflow. Without the If node, every item in a workflow would follow the same path. Most real-world automations need different handling based on the data. A lead scoring workflow might route high-value leads to a sales rep and low-value leads to an email nurture sequence. An invoice processing workflow might send invoices above a certain amount for manual approval while auto-approving smaller ones. A support ticket workflow might escalate urgent issues to a manager while sending routine requests to the standard queue. The If node supports string, number, and boolean comparisons: equals, not equals, greater than, less than, contains, starts with, ends with, is empty, and regex matching. You can combine multiple conditions with AND/OR logic. It processes each item individually, so in a batch of records, some might go down the true branch and others down the false branch. At Osher, the If node is part of nearly every workflow we build. Our talent marketplace application processing project used If nodes to route candidates based on qualification criteria. We use it across all our business automation and RPA projects wherever data-driven decisions need to happen without human intervention. If your workflows need conditional logic, talk to our n8n team about structuring your automations for reliable decision-making.
    If consultants
  • Eden AI integrations

    Eden AI integrations

    Eden AI is an API aggregation platform that gives developers access to multiple AI providers through a single, standardised interface. Instead of building separate integrations for OpenAI, Google Cloud Vision, AWS Textract, and other AI services, you connect to Eden AI once and switch between providers without changing your code. This matters for businesses that need AI capabilities like text analysis, image recognition, document parsing, or translation but don’t want to be locked into a single provider. Eden AI lets you compare results across providers, pick the best-performing one for your use case, and switch if pricing or quality changes. It covers categories including OCR, sentiment analysis, speech-to-text, object detection, and language translation. At Osher, we use Eden AI within n8n workflows when a client’s automation needs AI processing but the specific provider isn’t critical. For example, a document classification workflow might use Eden AI’s OCR endpoint to extract text, then route the output through a language model for categorisation. Our medical document classification project shows how we approach AI-powered document processing for clients. We also build custom AI solutions where Eden AI’s multi-provider approach reduces vendor lock-in risk. If you’re evaluating AI services and want to test multiple providers without building separate integrations for each one, talk to our team about how Eden AI fits into your automation stack.
    Eden AI integrations consultants

  • Start

    The Start node is the default entry point for manually triggered n8n workflows. Every n8n workflow needs a trigger to begin execution, and the Start node serves that role when you want to run a workflow by hand rather than on a schedule or in response to an external event. You click “Execute Workflow” in the n8n editor, and the Start node fires, passing control to the next node in the chain. While it might seem simple, the Start node plays an important role during workflow development and testing. When you’re building or debugging an automation, you run it manually dozens of times to check that each node behaves correctly. The Start node is what makes that possible. It’s also useful for workflows that are designed to be triggered on-demand by an operator, such as a monthly report generation workflow or a data cleanup script that a team member runs as needed. In production workflows, the Start node is typically replaced by a more specific trigger: a Webhook node for event-driven automations, a Cron node for scheduled runs, or an application-specific trigger like “new row in Google Sheets.” But during the build-and-test phase of any business automation project, the Start node is the tool you use constantly. At Osher, we use the Start node throughout the development process for every n8n project we build. If you’re exploring what n8n can automate in your business, get in touch and we’ll walk you through the platform.
    Start consultants
  • BugShot

    BugShot

    BugShot is a visual bug reporting tool that lets testers and team members capture screenshots, annotate them with markers and notes, and submit them directly to issue trackers without leaving the application they are testing. It provides browser extensions and integrations that streamline the path from “I found a problem” to “there is a ticket in Jira with all the details.” The problem BugShot addresses is the friction in bug reporting. Testers find an issue, take a screenshot, open their issue tracker, create a new ticket, upload the screenshot, type out the steps to reproduce, and add environment details. BugShot compresses this into a single flow: capture, annotate, and submit. Browser and device information is attached automatically. Osher includes tools like BugShot in development projects where QA efficiency directly affects delivery timelines. By reducing the time each bug report takes to file, testers can cover more ground during testing cycles. We connect BugShot’s output to your project management tools through our integration services, making sure reports land in the right project board with the right context attached.
    BugShot consultants
  • Adobe integrations

    Adobe integrations

    Adobe integrations connect Adobe’s creative and document tools (Photoshop, Illustrator, InDesign, Acrobat, Premiere Pro, After Effects, and others) with external business systems through APIs, webhooks, and workflow automation. Adobe provides several integration surfaces: Creative Cloud Libraries for shared assets, Adobe I/O APIs for programmatic access to individual products, Adobe Experience Platform for marketing data, and Adobe PDF Services for document generation and manipulation. The problem Adobe integrations solve is creative workflow fragmentation. Design teams produce assets in Adobe tools, but those assets need to flow into CMS platforms, DAM systems, marketing automation, print production, and e-commerce catalogues. Without integration, this transfer is manual: export, rename, upload, tag, publish. Adobe’s APIs make it possible to automate these steps, from asset creation through to final delivery. Osher connects Adobe’s APIs and export workflows into broader business automation systems. Common projects include automating document generation with Adobe PDF Services (generating contracts, reports, or invoices from templates), syncing creative assets from Adobe Libraries to web CMS or DAM platforms, and building automated data processing pipelines that extract text or metadata from PDF documents. Our team handles the API integration so your creative and operations teams can focus on their actual work.
    Adobe integrations consultants
  • Apiary integrations

    Apiary integrations

    Apiary (now part of Oracle) is an API design and documentation platform that lets teams write API specifications in API Blueprint or Swagger/OpenAPI format, generate interactive documentation from those specs, and run a mock server that returns sample responses before any backend code is written. It provides a collaborative environment where developers, product managers, and API consumers can design, review, and test APIs before committing to implementation. The problem Apiary solves is the “build first, document later” pattern that leads to poorly designed APIs. When teams jump straight into coding, API design decisions get made ad hoc and documentation becomes an afterthought. Apiary flips this by making the specification the starting point. You write the API contract, generate a mock server automatically, let consumers test against it, and only then build the real backend. This catches design problems early when they are cheap to fix. Osher uses API-first design principles in our custom development projects and recommends tools like Apiary when clients need clean API contracts for system integrations. Having a well-documented API spec before development starts reduces integration friction, speeds up parallel development (frontend and backend teams work simultaneously against the mock), and produces better documentation as a natural byproduct of the design process.
    Apiary integrations consultants
  • Spike

    Spike

    Spike is a conversational email and team messaging platform that turns traditional email inboxes into chat-style interfaces. Instead of formal email threads with headers and signatures, Spike presents messages as real-time conversations, combining email, group chat, video calls, and collaborative notes in a single app. It works with any existing email provider (Gmail, Outlook, IMAP) without requiring contacts to switch platforms. The core problem Spike addresses is email overload. Teams that rely heavily on email end up buried in long threads, duplicated information, and slow response loops. Spike strips away the formatting clutter and presents email as instant messaging, which speeds up internal communication while keeping the universal compatibility of email for external contacts. Osher integrates Spike into broader business automation workflows where communication triggers need to kick off downstream processes. For example, an incoming customer email in Spike can automatically create a support ticket, update a CRM record, or trigger a task assignment in your project management tool. Our system integration team connects Spike’s functionality to the rest of your tech stack so nothing falls through the cracks.
    Spike consultants
  • Rootly

    Rootly

    Rootly is an incident management platform that runs inside Slack. When something breaks in production, Rootly automates the incident response process: creating a dedicated Slack channel, paging on-call engineers, tracking status updates, coordinating communication with stakeholders, and generating post-incident reports, all without engineers leaving their primary communication tool. The problem Rootly addresses is the chaos that happens when systems go down. Without structured incident management, teams waste critical minutes figuring out who should be working on the problem, stakeholders do not know what is happening, and post-incident reviews lack the timeline data needed to prevent recurrence. Rootly brings order to this process by automating the operational overhead so engineers focus on fixing the issue. At Osher, we integrate Rootly with monitoring, alerting, and operations systems as part of our system integration work. Using n8n, we build pipelines that connect Rootly to monitoring tools (Datadog, PagerDuty, Grafana), ticketing systems (Jira, Linear), and status pages so that incidents are detected, managed, and documented automatically. We also build custom automation runbooks that Rootly can execute during incidents, reducing mean time to resolution. Rootly suits engineering and DevOps teams that manage production systems and need a structured, repeatable incident response process that works within their existing Slack-based communication workflow.
    Rootly consultants
  • Tuulio

    Tuulio

    Tuulio is an AI content generation platform that produces marketing copy, blog drafts, product descriptions, social media posts, and other written content using large language models. It provides templates and workflows for common content types, with controls for brand voice, tone, and output length. The content bottleneck is real for most marketing teams: they know they need more blog posts, email sequences, product descriptions, and social content, but they do not have enough writers to keep up with demand. Tuulio addresses this by generating first-draft content that human editors then refine and publish. It is a production accelerator, not a replacement for editorial judgement. At Osher, we integrate Tuulio into content production workflows as part of our business automation services. Using n8n, we build pipelines that trigger content generation based on business events (new product launch, campaign brief approval), route drafts through review and approval workflows, and publish approved content to CMS platforms or email tools automatically. We also connect Tuulio to SEO tools so generated content targets specific keywords and matches search intent. Tuulio suits marketing teams and content agencies that need to increase content output without proportionally increasing headcount, provided they maintain a human review step to ensure quality and brand consistency.
    Tuulio consultants