Full-Time
Posted on 10/1/2025
Automates cross-app workflows via Zaps
No salary listed
Remote in USA
Remote
Candidates must be based in the Americas.
Zapier is a software service that helps people connect different web apps so they can automate repetitive tasks. It works by letting users build
Company Size
1,001-5,000
Company Stage
Seed
Total Funding
$1.4M
Headquarters
San Francisco, California
Founded
2011
Help us improve and share your feedback! Did you find this helpful?
Work from anywhere
Competitive salary & bonus program
PTO
Health, dental, & vision coverage
Retirement plan with company match
Stock options
2 annual company retreats
Parental leave
Home office setup stipend
Professional development allowance
How to send QR alerts to Slack or Microsoft Teams using Zapier. By: Regie Update: May 03, 2026 QR TIGER integrates with Zapier to send real-time notifications to Slack or Microsoft Teams whenever someone scans a QR code or submits a vCard contact form. The workflow uses a QR TIGER event as the trigger and a channel message as the action. This helps sales, support, and event teams see new activity without checking the dashboard manually. This guide shows how to set up the trigger, customize the message, and route high-value events to the right channel. Table of Contents How to use QR TIGER events as Zapier triggers. This Zapier workflow uses QR TIGER as the trigger app. The trigger decides which QR activity starts the automation. You have two main trigger options: * New QR Scan: Sends a notification whenever someone scans your QR code. * New vCard Contact: Sends a message after someone submits details through a vCard contact form. Here is how to set it up: * On Zapier, click "Create Zap". * Click the "Untitled Zap" dropdown. * Select "Rename" and enter a clear Zap name. * Click the "Trigger" field. * Search and select QR TIGER QR Code. * Choose either "New QR Scan" or "New vCard Contact". * Run the trigger test. * Select a sample record so Zapier can pull the available fields. Steps to send instant alerts to Slack. After the trigger, add an action to send a notification to Slack when a QR code is scanned or when a new lead is submitted. For teams focused on Zapier and Slack integration, this action sends each QR interaction to the selected channel with the details your team needs. Here's how: 1. Add action * Click the plus icon under the QR TIGER trigger. * Search "Slack" and select the app. * Choose "Send Channel Message" as the action event. 2. Connect your Slack account * Under "Account", click "Sign in" to connect your Slack login account. * Approve the permission request. * Return to Zap and click "Continue". 3. Configure the message * Choose the channel. * For "Add Zapier app to channel automatically", choose "Yes". * In the "Message Text", write the message your team should receive. * Click the (+) icon to insert QR TIGER fields from the trigger. * For "Send as a bot?", choose "No" to send it through your connected account. You may also: * Choose "Yes" for "Send as a bot?", set a "Bot Name" and "Bot Icon". * Use "Include a link to this automation" to add the Zap link. * Use "Attach Image by URL" to add an image link. * Use "Auto-Expand Links" to control link previews. * Set "Link Usernames and Channel Names" to "Yes" for clickable mentions. * Use "Schedule At" to send the message later. * Use "File" to attach a file. * Use "Thread" to post inside an existing thread. 4. Test and publish * Run a test. * Check if the message shows the correct details. * If the test works, return to Zapier and publish the Zap. Sending instant alerts to Microsoft Teams. With Microsoft Teams integration, you can send new QR scans and leads straight to your chosen Team channel. Follow these steps to send QR code alerts to Microsoft Teams and allow members to see them right away. Follow these steps: 1. Add action * Add action under QR TIGER trigger. * Add the Teams app. * Choose "Send channel Message" action event. 2. Connect your account * Under "Account", click "Sign in". * Approve the permission request, then return to Zapier. * Click "Continue". 3. Configure the message * Choose the "Team" where the message should appear. * Select the "Channel" for the notification. * In "Message Text", write the message. * Click the plus icon to insert QR TIGER trigger fields. * For "Message Text Format", choose "Markdown" for cleaner spacing. * Click "Continue". 4. Test and publish * Run a test. * Confirm the message shows the right scan or lead details. * Return to Zapier and publish the Zap. Customizing messages by campaign or location. Your alert should show enough context for the team to act. Add campaign, location, device, or contact details in the message field. For "New QR Scan", useful fields include: * QR name * City * Region * Country * Device * QR ID * Short URL * Scanned at These fields help identify which campaign, branch, event booth, package, or store material drove the scan. For "New vCard Contact", useful fields include: * Name * Email * Phone * vCard ID * Created At * Submission ID These fields help your team trace which digital business card captured the lead. Example setups: * A location-focused scan notification might show the QR name, City, Country, Device, and Scanned at. * A campaign-focused contact might show the Name, Email, vCard ID, and Created At. Notifying teams of high-value QR events. Some QR campaigns need faster attention. Add a Filter step before the channel message action to send priority events to a specific team channel. For "New vCard Contact", use "vCard ID" to identify which vCard QR code should trigger a priority notification. For "New QR Scan", use fields such as QR name, City, Country, Region, QR ID, QR category, or Scanned at. Here is how to set the filter: 1. Under the QR TIGER trigger, add a "Filter" step. 2. In "Only continue if", choose the field you want to check: a. For lead notification = vCard ID b. For scan notification = Country, City, QR name, QR category, QR ID, or Scanned at 3. Choose the condition. a. Use "Exactly matches" or "Contains" for text fields. b. Use "After", "Before", or "Equals" for the "Scanned at" filter. 4. Enter the value that should trigger the priority. 5. Click "Continue" and test the filter. 6. Add the channel message action after the filter. 7. Choose the priority channel. 8. Write the message. 9. Run another test, then publish the Zap. This setup keeps general activity in one channel and sends high-value events to the people who need to respond first. Improving speed-to-response. Among practical Zapier use cases, this setup stands out for reducing the delay between a QR interaction and a team action. Once the Zap runs, each alert gives your team the context needed to decide the next step. * A sales team might follow up with a new vCard lead. * A support team might watch product-related scans. * An event team might track booth or location activity as scans come in. That helps your team: * Reply while interest is still high * Assign follow-ups faster * Track live campaign activity * Keep sales, support, and event teams aligned Want a live record of every QR lead in one place? Learn how to sync QR code data to Google Sheets using Zapier for easier tracking and reporting. Turn QR events into faster follow-ups. You now have a clear workflow for sending QR scan and vCard contact alerts to Slack or Microsoft Teams through Zapier. This setup gives your team faster visibility and a cleaner way to monitor QR activity without adding another manual task to the process. Once your alert workflow is live, every scan or lead becomes easier to track, assign, and act on. FAQs. How do I send alerts to Slack? You can send alerts to Slack by using an automation tool like Zapier. Set a trigger, choose Slack as the action app, then send the alert to a selected channel. Does Zapier integrate with Microsoft Teams? Yes. Zapier integrates with Microsoft Teams and can send messages to a chosen Teams channel when a trigger runs. How do I link Zapier to lead info? You link Zapier to lead info by setting your lead source as the trigger app, testing the trigger, and mapping the available data fields to the next action step.
Integrate to simplify: the new integration between inTouch and Zapier. Integrating different tools has always been one of the most complex aspects of digital projects. When systems do not communicate with each other, processes slow down, data gets scattered, and manual tasks increase. In this context, integrations are no longer optional: they are what truly allow systems to work together. inTouch is designed to integrate with other business systems through APIs and webhooks, connecting with CRMs, e-commerce platforms, and management software. But today, companies are asking for more: integrations that are simple, fast, and accessible even without development work. This is why Rdcom Global introduced the integration between inTouch and Zapier. Zapier and inTouch. Zapier makes it possible to connect thousands of applications and create automations quickly and easily, without writing any code. In practice, an event that happens in an external system can automatically trigger an action in inTouch: sending an SMS or an email, or updating contact lists. Some practical examples * By connecting inTouch to Google Sheets, every new contact added to a spreadsheet can be automatically imported into the platform. * If a customer abandons a cart on Ecwid, a Zap can trigger the sending of a follow-up email or SMS to recover the sale. * When a new landing page is published, a notification can be sent via inTouch to a team Slack channel. These are simple automations, but the same principle applies to more complex workflows. Zapier allows inTouch to be connected to e-commerce platforms, email services, spreadsheets, calendars, and CRMs, without technical skills. Thanks to ready-made templates, you only need to set the goal of the automation to get a pre-built flow structure, which can be customized in just a few steps. There are no additional costs for this service: you only need an inTouch account and a Zapier account. This type of integration helps automate repetitive tasks, improve productivity, and connect the tools already used within the company, adapting workflows to specific needs. Looking ahead. For rdcom, offering a platform that adapts to the systems already used by companies is an ongoing commitment. With Zapier, the direction is clear: making automations more accessible and immediate, while maintaining reliability and control.
Zapier has launched AI Guardrails, a safety tool that performs real-time checks within automated workflows to detect and block problematic AI outputs before they reach business systems. The feature addresses the gap between AI adoption and trust in AI-generated content. AI Guardrails operates inline within Zapier's platform, scanning for personally identifiable information across 30 categories, detecting prompt injection and jailbreak attempts, flagging toxic content, and analysing sentiment. Teams can add guardrail steps to any workflow and use results to route, block or escalate outputs without coding. The tool works across Zapier's ecosystem, including Zaps, Agents and Model Context Protocol-connected tools. It provides structured output for conditional logic, enabling automated enforcement of AI safety policies rather than relying on documentation alone. AI Guardrails is available now.
Bunny integrates with Zapier. Integrations Bunny now integrates with Zapier, the automation platform used by millions of businesses to connect their apps and streamline workflows. The integration allows teams to automatically create subscriptions in Bunny triggered by actions in any of Zapier's thousands of supported applications - no code required. Automate subscription creation. The Zapier integration adds a "Create Subscription" action to Bunny's app on Zapier. This means any event in your existing toolchain - a form submission, a CRM stage change, a new row in a spreadsheet - can instantly trigger a new subscription in Bunny. Manual data entry between disconnected systems becomes a thing of the past. For example, a B2B SaaS company could configure a Zap so that when a deal is marked as closed-won in their CRM, Bunny automatically provisions the customer's subscription with the correct plan and billing terms. The moment the deal closes, billing starts - with no manual handoff required. Another common use case is running multiple marketing campaigns simultaneously. If you have different landing pages targeting different segments - say, one for startups, one for enterprise, and one for a specific industry vertical - each page can have its own sign-up form. Each form submission triggers a separate Zap, and each Zap creates a trial subscription in Bunny with the plan and pricing that matches that audience. You get full flexibility in how you market and convert, without needing to build custom backend logic for each campaign. Simple setup. Setup is straightforward - install the Bunny app in Zapier, connect it to your Bunny account via the API, and you're ready to build. When creating a Zap, the Price List Code from Bunny's product catalog is entered as static text to ensure the correct subscription type is applied consistently, while customer details and other fields are mapped dynamically from whatever trigger you're using. Full setup instructions are available in the Bunny documentation. Get started. If you're already using Bunny, the Zapier integration is available now. If you're new to Bunny, book a demo to see how Bunny can automate your subscription billing from day one.
Zapier and Rillet connect ai-native ERP to broader finance stack. Adam Pitman Senior Editor, ERP Today and SAPinsider Key takeaways. Zapier and Rillet deliver AI-native finance ERP integration across more than 8,000 applications. The integration combines an AI-driven general ledger with orchestration to automate finance workflows and support continuous close processes. Finance teams can automate approvals, data synchronization, and cross-system coordination without custom development. Zapier and Rillet have partnered to connect an AI-native ERP platform with more than 8,000 business applications. The integration links Rillet's AI-driven general ledger with Zapier's orchestration layer, allowing finance teams to automate workflows across systems. The companies describe the combination as a way to extend AI beyond the ERP into finance. AI-Native ERP integration with Zapier orchestration platform. The integration connects Rillet's core accounting processes to external systems. Rillet manages financial logic inside the general ledger, while Zapier coordinates actions across other applications. The system enables workflows that move data and decisions between tools. Finance teams can sync transactions from billing, spend, and CRM systems into the ledger, route approvals through communication platforms, and trigger updates across systems without engineering support. AI agents operate across both layers. Rillet handles accounting tasks such as posting entries, reconciliations, and accrual logic, while Zapier orchestrates workflows, notifications, and multi-step processes across the broader application stack. Analysis. What this means for ERP insiders. ERP no longer needs to manage every workflow. The integration shows how finance workflows can run across systems rather than inside a single ERP. This creates a model where the ERP focuses on financial logic while orchestration layers handle coordination. Distributed finance architecture using ai-native ERP and orchestration layers. Traditional ERP models centralize workflows inside a single system, while this approach separates accounting logic from workflow coordination. Rillet operates as the system of record and decision engine. Zapier functions as the orchestration layer, connecting data, workflows, and AI agents across systems. This model supports a more distributed finance stack. Organizations can extend AI-driven processes across existing tools without replacing core systems, allowing finance teams to automate coordination work while maintaining control over financial data. Continuous close depends on connected systems. Rillet's continuous close model relies on real-time data from across the finance stack. Orchestration through Zapier helps ensure that transactions, approvals, and updates reach the ledger without delays or manual intervention. Automating finance workflows across ERP, CRM, and spend systems. The integration shifts how finance work is coordinated. Instead of relying on manual processes between systems, teams can automate how data, approvals, and updates move across the stack. This reduces operational friction. Tasks such as syncing transactions, routing approvals, and updating records across tools can run continuously, rather than depending on batch processes or manual intervention at the end of the period. The model also supports incremental adoption. Organizations can extend AI-driven workflows into existing environments without replacing core systems, using orchestration to connect finance processes across tools. This reflects a broader change in how finance systems are evolving. AI-native ERP platforms and orchestration layers are emerging together, separating financial logic from workflow execution and enabling more continuous, system-driven finance operations. AI in finance is expanding through orchestration layers. The partnership highlights how AI capabilities are extending beyond the ERP into connected systems. Orchestration platforms allow finance teams to apply AI across workflows while keeping financial logic anchored in the ledger. ERP Today covers how ERP, cloud, and AI change the way businesses run. Our editors speak with practitioners, vendors, and analysts to surface the technology, contracts, and risks that matter for enterprise leaders. Alongside our newsroom coverage, we run in-person summits where ERP leaders compare notes on programs like yours, and a research practice that turns reporting like this into organization-specific briefings and content.