AI & Automation

  • AWS Lambda

    AWS Lambda

    AWS Lambda is a serverless compute service from Amazon Web Services that runs code in response to events without requiring you to provision or manage servers. As an automation node, it allows workflows to execute custom functions written in Python, Node.js, Java, or other supported languages as part of a larger automation pipeline, handling processing tasks that go beyond what standard nodes can do. Development teams, data engineers, and technical operations staff use the AWS Lambda integration to run custom processing logic within their automation workflows. Complex data transformations, API calls to proprietary systems, machine learning model inference, and heavy computation tasks all run as Lambda functions that scale automatically based on demand. Osher integrates AWS Lambda into automation architectures where standard workflow nodes cannot handle the processing requirements. Our custom AI development team builds Lambda functions for running ML models on incoming data, processing large file transformations, executing complex business logic with custom validation rules, and connecting to legacy systems that require bespoke code to communicate with.
  • Google BigQuery

    Google BigQuery

    Google BigQuery is a serverless, highly scalable data warehouse built on Google Cloud. It enables SQL-based analysis of massive datasets — from gigabytes to petabytes — without managing infrastructure. BigQuery handles the compute resources automatically, so queries across billions of rows return results in seconds rather than hours. Data analysts, business intelligence teams, marketing analysts, and finance departments use BigQuery to centralise data from multiple sources and run complex analytical queries. Common use cases include combining Google Analytics data with CRM records, building revenue dashboards, analysing customer behaviour across touchpoints, running cohort analyses, and generating reports that would be too slow or impossible in a spreadsheet. At Osher, we connect BigQuery to your operational workflows so analytical insights translate into action. We build pipelines that load data from your CRM, advertising platforms, payment systems, and operational tools into BigQuery for unified analysis. Then we connect BigQuery outputs back to your business systems — query results can feed automated reports, trigger alerts when KPIs shift, update dashboards in real time, or push insights into your CRM for sales team action. Our AI consulting team also builds machine learning models that run directly on BigQuery data using BigQuery ML, enabling predictive analytics like churn scoring and demand forecasting without moving data out of your warehouse.
  • GitLab Trigger

    GitLab Trigger

    GitLab Trigger is the event-driven integration point for GitLab, a DevOps platform that combines source code management, CI/CD pipelines, issue tracking, and container registry into a single application. The trigger fires when specific events occur in your GitLab repositories — code pushes, merge requests, pipeline completions, issue updates, tag creation, and deployment status changes. Development teams, DevOps engineers, and engineering managers use GitLab triggers to connect their software development lifecycle to operational and business workflows. Instead of relying on developers to manually update project management tools, notify stakeholders, or trigger deployment processes, GitLab events can automatically drive those actions through automation workflows. At Osher, we connect GitLab triggers to your broader business systems so development activity flows into the tools your wider team uses. When a merge request is approved, our automations can update the related Jira or Asana task, notify the QA team in Slack, and log the change for compliance tracking. When a CI/CD pipeline fails, an alert can page the on-call engineer and create an incident ticket. When a release tag is pushed, deployment notifications go to stakeholders and release notes are compiled automatically. Our AI agent development team also builds intelligent GitLab integrations that use AI to review code changes, summarise merge requests, and flag potential issues before they reach production.
  • Mautic Trigger

    Mautic Trigger

    Mautic Trigger is the event-driven connector for Mautic, an open-source marketing automation platform. It fires when contacts interact with your marketing campaigns — opening emails, clicking links, submitting forms, visiting tracked pages, reaching lead scores, or moving through automated campaign workflows. Because Mautic is self-hosted, you retain full control over your contact data and marketing operations. Marketing teams, growth teams, and agencies that want marketing automation without per-contact SaaS pricing use Mautic. It provides email marketing, landing pages, lead scoring, contact segmentation, campaign workflows, and dynamic content — similar functionality to HubSpot or Marketo but with no per-contact fees and full data ownership. At Osher, we connect Mautic triggers to your CRM, sales tools, and operational systems so marketing engagement data drives business actions automatically. When a contact reaches a high lead score, our automations can create a qualified lead in Pipedrive, notify the assigned sales rep in Slack, and schedule a follow-up task. When a form submission arrives, the contact can be enriched with company data, segmented by interest, and routed to the right nurture campaign. Our AI agent development team also builds intelligent scoring models that use contact behaviour patterns from Mautic to predict purchase readiness, so your sales team focuses on the contacts most likely to convert.
  • Webflow Trigger

    Webflow Trigger

    Webflow Trigger is a webhook-based integration node that fires automated workflows whenever specific events occur on your Webflow site. It listens for form submissions, e-commerce orders, CMS item changes, membership signups, and site publish events, then passes that structured data directly into your automation pipeline for immediate processing. Marketing teams, e-commerce operators, and web agencies use Webflow Trigger to eliminate manual data handling between their website and backend systems. Instead of checking Webflow dashboards, exporting CSVs, or copying submission details into spreadsheets, every relevant event gets captured and processed automatically the moment it happens on your site. At Osher, we connect Webflow Trigger into broader automation workflows using n8n. A typical setup routes new form submissions to your CRM, syncs e-commerce orders with accounting software, updates inventory systems, and notifies your sales team via Slack or email. Our system integrations team builds these connections so your Webflow site becomes a fully integrated part of your business operations rather than an isolated website sitting apart from your core systems.
  • Pipedrive Trigger

    Pipedrive Trigger

    Pipedrive Trigger is the event-driven component of the Pipedrive CRM integration, enabling real-time responses to changes in your sales pipeline. When a deal moves stages, a contact is added, an activity is completed, or any other pipeline event occurs, the trigger fires and starts an automated workflow immediately. Sales teams and revenue operations managers use Pipedrive triggers to eliminate manual follow-up tasks and ensure nothing falls through the cracks during the sales process. Instead of relying on salespeople to remember every step after updating a deal, automations handle the downstream actions instantly — sending follow-up emails, notifying team members, updating external systems, or creating tasks in project management tools. At Osher, we build Pipedrive trigger workflows that connect your sales pipeline to every other system your team relies on. A deal reaching the ‘Won’ stage can automatically generate an onboarding project in Asana, create an invoice in Xero, add the customer to a Mailchimp welcome sequence, and notify the delivery team in Slack — all from a single pipeline update. We also use triggers for pipeline hygiene, flagging stale deals, sending manager alerts for high-value opportunities, and syncing deal data with reporting dashboards. Our sales automation services are designed to make your CRM the single source of truth that drives action across your entire organisation.
  • Kafka Trigger

    Kafka Trigger

    Apache Kafka Trigger is an event-driven connector that listens for messages on Kafka topics and initiates workflows when new data arrives. Kafka is a distributed event streaming platform designed for high-throughput, fault-tolerant data pipelines, processing millions of events per second across distributed systems. Engineering teams, data platform operators, and enterprises with real-time data requirements use Kafka to move data between microservices, feed analytics pipelines, and power event-driven architectures. Industries like financial services, logistics, telecommunications, and e-commerce rely on Kafka for use cases where data must flow continuously and reliably between systems. At Osher, we integrate Kafka triggers into business automation workflows so that streaming data can drive operational actions without custom code. When a Kafka topic receives a new message — a transaction event, sensor reading, inventory update, or user activity log — our automations pick it up and route it to the right destination. This might mean writing processed data to a database, sending alerts to operations teams, updating a dashboard, or triggering a downstream API call. Our custom AI development team also builds intelligent consumers that apply machine learning models to Kafka streams, enabling real-time scoring, classification, and anomaly detection on your event data as it flows through.
  • Mailjet

    Mailjet

    Mailjet is a cloud-based email delivery service that handles both transactional emails (order confirmations, password resets, account notifications) and marketing campaigns. It provides a drag-and-drop email builder, contact management, A/B testing, real-time analytics, and a robust sending API capable of handling high email volumes with strong deliverability rates. SaaS companies, e-commerce platforms, and development teams use Mailjet for its developer-friendly API and reliable transactional email delivery. Unlike purely marketing-focused platforms, Mailjet excels at sending time-sensitive, automated emails that need to arrive quickly and consistently — receipts, shipping notifications, two-factor authentication codes, and system alerts. At Osher, we integrate Mailjet into automated business workflows so email sending becomes part of a larger operational process rather than a standalone action. We connect Mailjet to your CRM, e-commerce platform, and internal systems so that the right emails go out at the right time based on real events. A completed purchase triggers an order confirmation through Mailjet. A support ticket resolution sends a satisfaction survey. A subscription renewal date approaching triggers a reminder sequence. Our robotic process automation services connect Mailjet to your full business process, ensuring transactional and marketing emails are sent reliably without manual intervention or custom code.
  • Elasticsearch

    Elasticsearch

    Elasticsearch is a distributed search and analytics engine built on Apache Lucene. It stores, indexes, and queries large volumes of structured and unstructured data with sub-second response times. Beyond full-text search, Elasticsearch powers log analytics, application performance monitoring, security event analysis, and business intelligence dashboards. Engineering teams, DevOps engineers, data analysts, and security operations teams use Elasticsearch as the backbone for search-driven applications and observability platforms. Common deployments include website search bars, product catalogue search, centralised log management (often as part of the ELK stack), and real-time monitoring dashboards that track system health and business metrics. At Osher, we connect Elasticsearch to business automation workflows so your indexed data can drive operational actions. When Elasticsearch detects a spike in error logs, our automations can page the on-call engineer, create a Jira ticket, and post details to a Slack channel. When product search analytics reveal trending queries, we can update your CRM or marketing tools with those insights. We also build workflows that feed data into Elasticsearch from multiple business systems, creating a unified search layer across your CRM, support tickets, documents, and product catalogue. Our automated data processing team handles the full pipeline — ingesting data into Elasticsearch, building queries, and connecting search results to downstream business actions.
  • Mailchimp

    Mailchimp

    Mailchimp is an email marketing platform used by businesses to create, send, and track email campaigns, automated sequences, and audience segmentation. It provides tools for designing newsletters, managing subscriber lists, running A/B tests, and analysing campaign performance through open rates, click rates, and revenue attribution. Small and mid-sized businesses, e-commerce stores, and marketing teams rely on Mailchimp to stay in touch with customers and prospects. Common use cases include welcome email sequences, promotional campaigns, abandoned cart reminders, and regular newsletter distribution to segmented audiences. At Osher, we connect Mailchimp to your broader business systems so email marketing works as part of a unified workflow rather than a standalone silo. We build automations that sync subscriber data between Mailchimp and your CRM, trigger email sequences based on events from other platforms (form submissions, purchases, support tickets), and push campaign analytics into centralised dashboards. For instance, when a lead fills out a form on your website, our automation can add them to the right Mailchimp audience segment, tag them based on their enquiry type, and kick off a targeted nurture sequence — all without manual data entry. Our business automation team builds these workflows to eliminate the repetitive tasks that slow down your marketing operations.
  • Asana

    Asana

    Asana is a project management platform that helps teams organise work into projects, tasks, subtasks, and milestones. It provides multiple views — list, board, timeline, and calendar — along with features for assigning ownership, setting due dates, tracking progress, and managing workloads across team members. Operations teams, marketing departments, product teams, and agencies use Asana to coordinate work across people and departments. Common use cases include campaign management, sprint planning, client onboarding processes, content calendars, and cross-functional project tracking where visibility and accountability matter. At Osher, we connect Asana to the rest of your business tools so project updates flow automatically without manual status meetings or copy-paste updates. We build automations that create Asana tasks from external events — a new CRM deal creates an onboarding project, a support ticket spawns a bug fix task, a form submission generates a content brief. We also push Asana data outward, sending task completion notifications to Slack, updating client-facing dashboards when milestones are reached, or syncing project timelines with resource planning tools. Our automated data processing services ensure information moves between Asana and your other systems accurately, so your team spends time on the work itself rather than updating multiple tools about the work.
  • Mailgun

    Mailgun

    Mailgun is a transactional email API built for developers and businesses that need reliable, high-volume email delivery. Unlike marketing email platforms, Mailgun focuses on sending emails triggered by application events: password resets, order confirmations, invoice delivery, and automated notifications. The Mailgun node lets your automation workflows send, receive, and track emails programmatically through the Mailgun API. Businesses use Mailgun in their automations to send personalised transactional emails at scale, process incoming emails as workflow triggers, track delivery and engagement metrics, and manage suppression lists. It is a popular choice for SaaS companies, e-commerce platforms, and any organisation that needs to send emails from automated systems rather than manually from a marketing tool. Osher integrates Mailgun into automated data processing workflows where email is a key communication channel. We build systems that generate and send emails based on real business events, whether that is a completed form submission, a status change in your CRM, or an AI-processed document that needs to be delivered. Every email is tracked, and bounce and complaint data feeds back into your systems to keep your sender reputation healthy.
  • Matrix

    Matrix

    Matrix is an open, decentralised communication protocol that provides end-to-end encrypted messaging, voice, and video. Unlike proprietary platforms, Matrix lets organisations run their own servers while still communicating with users on other Matrix servers through federation. The Matrix node allows automation workflows to send messages, manage rooms, invite users, and interact with the Matrix network programmatically. Organisations that require sovereign communications use Matrix for its encryption, self-hosting capability, and federation model. Automation use cases include posting system alerts and monitoring notifications to Matrix rooms, creating dedicated rooms for projects or incidents, bridging messages between Matrix and other platforms, and building bot-driven workflows that respond to commands in chat. Osher builds AI agent workflows that interact through Matrix for organisations where data sovereignty and end-to-end encryption are non-negotiable. We connect your internal systems to Matrix rooms so operational notifications, alerts, and AI-generated insights arrive securely in the channels where your team operates. For defence, government, and regulated industries, Matrix provides the communication backbone that proprietary tools cannot match on security and data control.
  • HubSpot Trigger

    HubSpot Trigger

    HubSpot Trigger is an automation node that fires whenever specific events occur in your HubSpot CRM. It detects new contacts, deal stage changes, form submissions, company updates, and other CRM events in real time, then passes that data into your workflow for processing. Marketing and sales teams use it to build instant-response automations that act the moment something changes in HubSpot. Practical use cases include triggering personalised email sequences when a contact reaches a certain lifecycle stage, notifying sales reps the instant a deal moves to a new pipeline stage, syncing HubSpot form submissions to external databases, and creating tasks in project management tools when deals close. The trigger removes the delay between a CRM event and the action your team needs to take. Osher builds sales automation workflows that respond to HubSpot events within seconds. We connect your CRM triggers to email systems, Slack notifications, quoting tools, and onboarding workflows so nothing falls through the cracks between deal stages. When a lead fills out a form, books a call, or moves through your pipeline, the right follow-up actions happen automatically without your team needing to remember or manually initiate them.
  • Compare Datasets

    Compare Datasets

    Compare Datasets is a workflow node that takes two sets of data and identifies the differences between them. It compares records field by field and outputs three groups: items that exist only in the first dataset, items that exist only in the second dataset, and items that exist in both but have different values. Data teams, operations managers, and finance departments use it to catch discrepancies between systems without manually cross-referencing spreadsheets. Common use cases include reconciling CRM records against billing system data, identifying new or removed products between catalogue versions, detecting changes in employee records across HR systems, and verifying that data migrations transferred all records correctly. Any time you need to answer the question “what changed between these two sets of data?”, this node handles it programmatically. Osher uses Compare Datasets as a core component in automated data processing workflows that keep multiple systems in sync. We build reconciliation pipelines that pull data from two or more sources, compare them automatically, and take action on the differences: creating missing records, flagging discrepancies for review, or updating stale data. This replaces the manual spreadsheet comparisons that consume hours of your team’s time every week. See how we applied similar data reconciliation techniques in our BOM weather data pipeline project.
  • RabbitMQ

    RabbitMQ

    RabbitMQ is an open-source message broker that sits between services in your software architecture and handles the reliable delivery of messages between them. Instead of Service A calling Service B directly (and failing if B is down or overloaded), Service A publishes a message to RabbitMQ, and Service B consumes it when ready. This decoupling makes systems more resilient, scalable, and easier to maintain. RabbitMQ supports the AMQP protocol and offers features like message persistence, routing, dead-letter queues, and clustering for high availability. The n8n RabbitMQ node lets workflows publish messages to RabbitMQ queues and consume messages from them. This is valuable when n8n is part of a larger microservices architecture — it can consume messages published by other services (e.g., a new order event from your e-commerce platform) and trigger automations, or it can publish messages that other services pick up (e.g., sending a processed data payload to a downstream service for further handling). At Osher, we use RabbitMQ with n8n for clients who have event-driven architectures or need reliable message delivery between systems that process data at different speeds. If your backend services need to communicate reliably without tight coupling, or if you need n8n to process events from a message queue rather than polling APIs, our system integration services can architect and implement the RabbitMQ layer that ties everything together.
  • Jira Trigger

    Jira Trigger

    Jira Trigger is an automation node that fires whenever specific events occur in your Jira project management boards. It listens for new issues, status changes, comment additions, and sprint updates, then passes that data into your workflow for processing. Teams running agile development cycles use Jira Trigger to eliminate the manual checking and copy-pasting that slows down cross-tool communication. Common use cases include syncing new Jira tickets to Slack channels, updating external spreadsheets when issue statuses change, and routing bug reports to the right team based on priority or label. QA teams use it to kick off automated testing pipelines the moment a ticket moves to “Ready for QA”, while project managers rely on it to keep stakeholders informed without writing status emails. At Osher, we connect Jira Trigger into broader system integration workflows that tie your project management stack to CRMs, communication tools, and reporting dashboards. Rather than building fragile point-to-point connections, we design event-driven automations that scale as your team grows. The result is fewer missed updates, faster response times, and a project management setup that actually reflects what your team is doing in real time.
  • Supabase

    Supabase

    Supabase is an open-source backend platform that provides a PostgreSQL database, authentication, real-time subscriptions, and file storage through a single API. Developers and product teams use it as a faster alternative to building backend infrastructure from scratch, while retaining full control over their data. The Supabase node lets you read, write, update, and delete database records directly from your automation workflows. Typical automation use cases include syncing form submissions into Supabase tables, pushing CRM updates into a centralised database, triggering workflows when new rows appear, and backing up data from third-party APIs into structured storage. Startups and mid-size companies often use Supabase as their application database, which makes it a natural integration point for connecting frontend apps with backend automation logic. Osher builds custom AI and automation solutions that use Supabase as the data layer. We connect your Supabase tables to workflow engines, AI processing pipelines, and business applications so your data moves where it needs to go without manual exports or fragile scripts. Whether you need real-time data syncing, automated record management, or AI-powered processing of your database contents, we design systems that treat your Supabase instance as a living, connected part of your tech stack.
  • Calendly Trigger

    Calendly Trigger

    Calendly Trigger is an automation node that fires whenever a scheduling event occurs in your Calendly account. It detects new bookings, cancellations, and reschedules in real time, then passes the appointment details into your workflow for processing. Sales teams, consultants, and service businesses use it to eliminate the manual follow-up steps that happen after someone books a meeting. Practical use cases include automatically adding new bookings to your CRM, sending personalised confirmation messages via email or SMS, creating preparation tasks in your project management tool, and updating availability trackers. When a meeting is cancelled, the trigger can notify your team, remove calendar blocks, and update pipeline stages without anyone lifting a finger. Osher builds sales automation workflows that start the moment a prospect books a call through Calendly. We connect your scheduling data to your CRM, email sequences, and internal tools so your team walks into every meeting prepared. No more manually copying booking details between systems or forgetting to send pre-call questionnaires. The entire booking-to-meeting pipeline runs automatically.
  • MQTT

    MQTT

    MQTT (Message Queuing Telemetry Transport) is a lightweight messaging protocol designed for devices with limited processing power and networks with constrained bandwidth. It uses a publish-subscribe model: devices publish messages to a topic on a central broker, and any client subscribed to that topic receives the message. MQTT runs over TCP/IP and is the dominant protocol for IoT (Internet of Things) communication, used in everything from factory sensor networks to smart building systems. The n8n MQTT node allows workflows to subscribe to MQTT topics and trigger automations when messages arrive, or publish messages to topics as part of a workflow. This makes it possible to connect IoT device data to business systems — for example, reading temperature sensor data from a warehouse and triggering an alert in Slack, or receiving machine status updates from factory equipment and logging them to a database for reporting. At Osher, we use the MQTT node in n8n to bridge the gap between operational technology (sensors, PLCs, edge devices) and business systems (databases, dashboards, notification channels). If your business collects data from physical devices and you are manually exporting or checking it, our system integration services can connect those data streams directly into your workflows so the information reaches the right people and systems in real time.
  • Home Assistant

    Home Assistant

    Home Assistant is an open-source home and building automation platform that runs locally on your own hardware (Raspberry Pi, mini PC, NAS, or virtual machine). It connects to over 2,000 device types — smart lights, thermostats, security cameras, door locks, energy monitors, HVAC systems, and industrial sensors — and provides a single interface for monitoring and controlling all of them. Unlike cloud-dependent platforms, Home Assistant processes everything locally, which means faster response times, no subscription fees, and full data privacy. The n8n Home Assistant node lets you read device states, trigger automations, call services, and fire events from within an n8n workflow. This bridges the gap between building/facility automation and business systems. For example, you can trigger an n8n workflow when a meeting room sensor detects occupancy, log energy consumption data from smart meters into a database for reporting, or send an alert to your facilities team when a temperature sensor exceeds a threshold. At Osher, we connect Home Assistant to business workflows for clients who need their physical environment data to feed into operational systems. This is relevant for commercial offices, warehouses, retail spaces, and any facility with smart devices. If you are running Home Assistant but the data stays siloed in the Home Assistant dashboard, our system integration services can connect it to your business tools so the data drives real actions.
  • Trello Trigger

    Trello Trigger

    The Trello Trigger node in n8n monitors your Trello boards for changes and starts a workflow whenever a specified event occurs. Supported events include card creation, card movement between lists, card updates, comment additions, checklist completions, due date changes, and member assignments. When the trigger fires, it passes the full card data (title, description, labels, members, custom fields) into the workflow for processing. This node is useful for teams that use Trello as their project management or task tracking tool but need board changes to trigger actions in other systems. For example, moving a card to a “Ready for Invoice” list can trigger an n8n workflow that creates a draft invoice in Xero. A new card in a “Bug Reports” list can create a ticket in Jira or send a formatted alert to a Slack channel. A due date change can update a Google Calendar event or send a reminder email to the assigned team member. At Osher, we use the Trello Trigger node for clients who want their Trello boards to drive real business actions rather than just track tasks visually. If your team is manually checking Trello for updates and then copying information into other tools, our business automation services can wire up those connections so moving a card in Trello automatically does the downstream work.
  • Github Trigger

    Github Trigger

    GitHub Trigger is an n8n node that starts a workflow whenever a specific event happens in your GitHub repositories — pushes, pull requests, issues, releases, code reviews, or any of the dozens of webhook events GitHub supports. If your development team uses GitHub and you want automated actions to happen when code is pushed, PRs are opened, or issues are created, this trigger connects your code repository to your operational workflows. The problem this solves is the disconnect between development activity and business operations. When a developer pushes code or a PR gets merged, other things usually need to happen — deployment notifications sent to the team, release notes posted, JIRA tickets updated, clients notified of new features, or QA tasks created. Doing these manually is error-prone and slow. The GitHub Trigger fires automatically and kicks off whatever downstream actions you define in n8n. At Osher Digital, we use the GitHub Trigger node as part of system integration projects that connect development workflows to business tools. Common builds include posting deployment summaries to Slack or Mattermost when code is merged to main, creating project management tasks when new issues are filed, syncing release notes to a client-facing changelog, and triggering automated test or build pipelines. If your dev team lives in GitHub but your business runs on different tools, this trigger bridges the gap.
  • Spotify

    Spotify

    The Spotify node in n8n lets you interact with the Spotify Web API to retrieve track, album, artist, and playlist data, manage playlists, and pull listening analytics. If you run a business that involves music — retail environments, hospitality venues, fitness studios, event companies, or media agencies — this node connects Spotify’s catalogue and playlist management to your automation workflows. The practical problem this node solves is manual playlist and music data management. If your marketing team tracks trending songs for social content, if your venues need playlists updated based on time of day or day of week, or if you need to pull listening data for reporting, doing that manually through Spotify’s app is tedious and inconsistent. The n8n Spotify node automates those tasks so they run on schedule without human intervention. At Osher Digital, we use the Spotify node in business automation workflows for clients who manage music as part of their business operations. Use cases include automatically updating venue playlists based on scheduling rules, pulling artist and track data for media reporting, syncing playlist contents with content management systems, and building music recommendation feeds for apps or websites. If music data or playlist management is part of your workflow, we connect it to the rest of your systems through n8n.
  • ActiveCampaign

    ActiveCampaign

    ActiveCampaign is a customer experience automation platform that combines email marketing, marketing automation, sales CRM, and transactional email into a single tool. It is used by over 180,000 businesses globally to send targeted email campaigns, score and route leads, build multi-step automation sequences, and track deal pipelines. The platform stands out for its automation builder, which uses a visual drag-and-drop interface to create conditional workflows triggered by subscriber behaviour, site visits, purchases, or custom events. For Australian businesses running complex customer journeys across email, SMS, and web, ActiveCampaign is a strong mid-market choice that sits between basic tools like Mailchimp and enterprise platforms like HubSpot or Marketo. Its native CRM module tracks deals through custom pipelines, while its machine learning features (predictive sending, win probability scoring) help sales and marketing teams focus effort where it counts. At Osher, we integrate ActiveCampaign with n8n workflows to build automations that go well beyond what the platform can do on its own. Common builds include syncing ActiveCampaign contacts bi-directionally with external databases, triggering deal stage updates from form submissions or payment events, and pushing lead scores into Slack for real-time sales alerts. If your team is spending hours on manual list management or chasing cold leads, our sales automation services can connect ActiveCampaign to the rest of your tech stack and eliminate the busywork.
  • Workflow Trigger

    The Workflow Trigger node is an internal n8n component that starts a workflow based on a call from another workflow. Unlike external triggers (webhooks, scheduled timers, or app-specific events), the Workflow Trigger sits inside a sub-workflow and waits to be invoked by a parent workflow using the Execute Workflow node. This is how you break large, complex automations into smaller, reusable pieces. If you have built an n8n automation that has grown to dozens of nodes and become difficult to maintain, sub-workflows with Workflow Triggers are the fix. Common patterns include: a data validation sub-workflow called by multiple parent workflows, an error handling routine shared across your entire n8n instance, or a notification sub-workflow that formats and sends alerts to Slack, email, or SMS depending on the input it receives. At Osher, we use sub-workflow architecture in nearly every client project. It makes automations easier to test (you can run the sub-workflow in isolation), easier to debug (each piece has its own execution log), and easier to update (changing the sub-workflow updates every parent that calls it). If your n8n instance has become a tangle of duplicated logic across dozens of workflows, our n8n consulting team can restructure it into a clean, maintainable architecture using Workflow Triggers and sub-workflows.
  • Google Drive Trigger

    Google Drive Trigger

    Google Drive Trigger is an n8n node that kicks off automated workflows whenever something changes in your Google Drive. It watches for new files landing in a folder, edits to existing documents, or files being moved or deleted — then fires your workflow instantly. If your team dumps client briefs, signed contracts, or raw data files into shared Drive folders and someone still has to manually sort, rename, or forward those files, this trigger removes that bottleneck entirely. Google Drive is already where most teams store and share documents. The problem is that Drive on its own does not connect to your CRM, your project management tool, or your data pipeline. The Google Drive Trigger in n8n bridges that gap. When a new file appears, n8n can automatically extract text from it, push the data into your database, notify your team on Slack, or run it through an AI classification model — all without anyone lifting a finger. At Osher Digital, we use the Google Drive Trigger node regularly when building automated data processing workflows for Australian businesses. Common setups include watching an uploads folder for incoming invoices, triggering OCR and data extraction when scanned documents arrive, and automatically filing processed documents into the correct subfolders. If your business runs on Google Workspace and you are tired of manual file handling, this is the node that makes it go away.
  • MQTT Trigger

    MQTT Trigger

    MQTT Trigger is an n8n node that starts a workflow whenever a message arrives on a specific MQTT topic. MQTT (Message Queuing Telemetry Transport) is a lightweight messaging protocol built for IoT devices, sensors, and machine-to-machine communication. If you have temperature sensors, GPS trackers, industrial equipment, or smart building systems publishing data over MQTT, this trigger node lets n8n listen for those messages and act on them automatically. The practical problem MQTT Trigger solves is connecting IoT and operational technology (OT) data to your business systems. Your sensors might be publishing readings every few seconds, but that data is useless sitting on an MQTT broker. The MQTT Trigger node in n8n picks up those messages and routes them into databases, dashboards, alerting systems, or AI models for analysis — turning raw device data into actionable business intelligence. At Osher Digital, we use the MQTT Trigger node when building system integrations that bridge the gap between physical infrastructure and business software. This includes monitoring environmental sensors for compliance reporting, tracking asset locations in real time, and triggering maintenance workflows when equipment readings fall outside normal ranges. If your organisation has IoT devices generating data that nobody is acting on, this is where we start.
  • RabbitMQ Trigger

    RabbitMQ Trigger

    RabbitMQ Trigger is an n8n node that starts a workflow whenever a new message arrives in a RabbitMQ queue. RabbitMQ is an open-source message broker used by development teams to decouple services, manage background job queues, and handle asynchronous processing. If your engineering team already uses RabbitMQ to pass messages between microservices, this trigger lets n8n listen to those queues and execute automation workflows in response. The core problem this solves is getting business logic and operational workflows connected to your message queue infrastructure. Developers build RabbitMQ queues for technical reasons — handling order processing, managing email queues, distributing background tasks — but the business side needs visibility and action. The RabbitMQ Trigger bridges that gap by letting n8n consume messages from any queue and route them into CRM updates, notification systems, reporting dashboards, or any other business tool. At Osher Digital, we use the RabbitMQ Trigger when clients have existing message queue infrastructure and need to connect it to business workflows without writing custom code. This fits into our system integration work, where we connect developer-facing infrastructure to business-facing tools. Common use cases include processing order events from an e-commerce backend, handling webhook retries through a dead-letter queue, and orchestrating multi-step data processing pipelines.
  • Typeform Trigger

    Typeform Trigger

    Typeform Trigger is an n8n node that fires a workflow every time someone submits a response to one of your Typeform forms. Instead of manually checking Typeform for new submissions, exporting CSVs, or copying responses into your CRM by hand, the trigger pushes each response into n8n the moment it arrives. From there, the data can flow automatically into your sales pipeline, email sequences, databases, or any other system. Typeform is popular because it creates forms that people actually finish — the conversational, one-question-at-a-time format gets higher completion rates than traditional forms. But the data those forms collect is only useful if it reaches the right system quickly. If your team is manually downloading Typeform responses and re-entering them into spreadsheets or CRMs, the Typeform Trigger eliminates that delay and the errors that come with manual data entry. At Osher Digital, we connect Typeform to downstream systems as part of our sales automation and business automation projects. Typical setups include routing lead capture form submissions into HubSpot or Pipedrive with automatic lead scoring, sending personalised confirmation emails based on form answers, and creating tasks in project management tools when onboarding forms are completed. If you use Typeform to collect any kind of business-critical data, we make sure that data reaches its destination automatically.
  • Twilio

    Twilio

    Twilio is a cloud communications platform that provides APIs for sending and receiving SMS messages, making and receiving phone calls, sending WhatsApp messages, and handling video. Rather than building telephony infrastructure or negotiating carrier agreements, developers use Twilio’s APIs to add communication capabilities to their applications programmatically. You get a phone number from Twilio, and then use their API to send messages or handle incoming calls with webhooks. The problem Twilio solves is communication at scale. When a business needs to send appointment reminders via SMS, verify phone numbers with one-time codes, notify field workers about new jobs, or route incoming calls to the right department, doing this manually does not scale. Twilio makes these interactions programmable — triggered by events in your other systems. In n8n, the Twilio node can send SMS and WhatsApp messages using Twilio’s Messaging API. This makes it straightforward to add SMS notifications to any automation workflow — send an alert when a monitoring check fails, confirm an appointment when a calendar event is created, or notify a sales rep when a high-value lead comes in. Incoming messages can trigger n8n workflows via Twilio webhooks. Osher integrates Twilio into business automation projects where clients need SMS or WhatsApp as part of their workflows. We also use it for AI agent systems that communicate with users via text message, and in sales automation setups where lead notifications need to reach people on their phones immediately.
  • Airtable Trigger

    Airtable Trigger

    The Airtable Trigger node in n8n monitors an Airtable base for record changes and starts a workflow when those changes occur. Airtable itself is a spreadsheet-database hybrid — it looks like a spreadsheet but supports relational links between tables, attachment fields, single/multi-select fields, and a proper API. The trigger node watches a specific table and fires when records are created or updated, passing the changed record data into your n8n workflow for processing. The problem this solves is keeping Airtable in sync with everything else. Teams often use Airtable as their central tracker for projects, inventory, content calendars, or CRM contacts. When someone adds or changes a record in Airtable, other systems need to know — a Slack message needs sending, a task needs creating in another tool, or data needs updating in a database. Without the trigger, someone has to manually copy that information between systems. The Airtable Trigger node polls the Airtable API at a configurable interval, checking a specified view for new or modified records. When it finds changes, it outputs the full record data (all fields) to the next node in the workflow. This lets you build reactive automations that respond to your team’s activity in Airtable without anyone needing to leave the spreadsheet interface. Osher uses Airtable triggers in system integration projects where Airtable is the team’s primary data entry point. We also build business automation workflows that react to Airtable changes to update CRMs, send notifications, or feed data into processing pipelines.
  • WooCommerce Trigger

    WooCommerce Trigger

    The WooCommerce Trigger node in n8n listens for events from a WooCommerce store and starts a workflow when those events occur. WooCommerce is the most widely used e-commerce plugin for WordPress, and its webhook system can notify external services whenever orders are placed, products are updated, customers register, or coupons are used. The trigger node receives these webhook payloads and passes the full event data into your n8n workflow. The problem this solves is the gap between your online store and your other business systems. When a customer places an order, several things need to happen: the order data should reach your accounting software, the warehouse needs a pick list, the customer should get a confirmation (possibly via SMS), and your CRM should log the purchase. WooCommerce handles the storefront, but it does not natively push data to all these other systems. The trigger node bridges that gap. WooCommerce webhooks fire in near real-time when events happen — order created, order updated, order deleted, product created, product updated, customer created, and coupon events. The trigger node receives the full payload including all order line items, customer details, shipping information, and payment status. This gives your n8n workflow everything it needs to route the data to the right downstream systems. Osher integrates WooCommerce stores into business automation workflows that connect orders to fulfillment, accounting, and customer communication systems. We also build system integrations that keep WooCommerce product and inventory data synchronised with external platforms.
  • Google Calendar Trigger

    Google Calendar Trigger

    The Google Calendar Trigger node in n8n monitors a Google Calendar for event changes and starts a workflow when events are created, updated, or deleted. Google Calendar is the scheduling backbone for most organisations using Google Workspace, and the trigger node turns calendar activity into automated actions — sending preparation materials before meetings, notifying team members about schedule changes, logging meeting data to a CRM, or triggering follow-up tasks after events end. The problem this solves is the disconnect between scheduling and action. When someone books a meeting, several things often need to happen: a briefing document needs sending, a room or resource needs confirming, attendees need reminders via a different channel, or follow-up tasks need creating after the meeting concludes. Without automation, someone has to remember to do each of these things manually. The Google Calendar Trigger connects via OAuth2 to a Google account and polls a specified calendar for changes at a configurable interval. When it detects new, updated, or cancelled events, it passes the event data — title, description, start/end times, attendees, location, and custom properties — to the next node in the workflow. This gives you everything you need to build scheduling-driven automations. Osher uses Google Calendar triggers in business automation projects where meeting schedules drive downstream workflows. We also build system integrations that keep calendars synchronised with CRMs, project management tools, and communication platforms.
  • Gmail Trigger

    Gmail Trigger

    The Gmail Trigger node in n8n monitors a Gmail inbox for new emails matching specified criteria and starts a workflow when matching messages arrive. Gmail is the email platform for Google Workspace (and personal Google accounts), and the trigger turns incoming email into automated action — routing support requests to a ticketing system, extracting data from structured emails, forwarding attachments to cloud storage, or notifying teams about important messages in Slack. The problem this solves is manual email triage. Many business processes still run on email: customers send enquiries, suppliers send invoices, partners send reports, systems send alerts. Someone has to read each email, decide what to do with it, and then take action in another system. The Gmail Trigger automates that first step — detecting the right emails and kicking off the appropriate workflow. The trigger connects via OAuth2 to a Gmail account and polls for new messages at a configurable interval. You can filter by label, sender, subject keywords, or other Gmail search criteria. When matching emails arrive, the trigger outputs the message data — subject, body (plain text and HTML), sender, recipients, date, attachments, and Gmail labels — to the next node in your workflow. Osher uses Gmail triggers in business automation projects where email is a key input channel. We also build AI agent workflows that use the Gmail Trigger to process incoming emails with AI — classifying intent, extracting structured data, and routing to the right team or system automatically.
  • Local File Trigger

    The Local File Trigger node in n8n watches a folder on your server’s file system and starts a workflow whenever a file is created, modified, or deleted. It turns your file system into an event source: drop a file into a watched folder and n8n automatically picks it up and processes it. This is particularly useful for businesses that receive data as files: CSV exports from legacy systems, PDF invoices from suppliers, XML feeds from government portals, or images that need processing. Instead of someone manually checking a folder, opening each file, and entering data into another system, the Local File Trigger detects new files immediately and kicks off the processing workflow. The node monitors a specified directory path and can filter by file extension. When it detects a change, it outputs the file path, file name, and event type (created, changed, deleted). You then use subsequent nodes (Read Binary File, Spreadsheet File, CSV, or code nodes) to read and process the file contents. At Osher, we use the Local File Trigger in automated data processing workflows where files arrive from external systems via SFTP, shared drives, or manual uploads. A typical build watches an SFTP landing folder, picks up new CSV files, parses the data, validates it, and loads it into a database or CRM. Our RPA team uses this pattern to replace manual file-processing tasks across finance, operations, and admin teams.