Help center Core configuration Integrations & migrations Connect Supportbench workflows through Zapier Updated Wednesday, October 28, 2026 · Marc Staine Use Zapier to connect supported Supportbench triggers and actions with another operational system. This Supportbench page is an installation entry point and workflow reference; build, map and test the actual Zap in Zapier. Start with one clearly defined customer-support outcome and verify the resulting record before enabling repeated execution. Applies to: Supportbench Core. Location: Settings → Integrations → Zapier. Integration administration and the intended Zapier workspace access are required. Before you begin Identify the intended Zapier workspace, workflow owner, input source and expected Supportbench result. Confirm you may connect the two systems and use the chosen test data.Review Supported workflows on this page and the actual trigger/actions offered in your Zapier editor. A listed use case is not a guarantee that every possible field or event is supported.Prepare a synthetic or otherwise approved test record. Decide how you will recognize a successful result and detect a duplicate before repeating a write test. Configure and verify Open Settings → Integrations → Zapier and review Supported workflows. The page describes creating cases, creating activities, looking up customers and triggering automation when cases are updated.Choose Install Supportbench in Zapier. It opens Zapier in a new tab; confirm you are in the intended workspace.In Zapier, create or open the intended Zap and select a supported Supportbench trigger or action. Sign in to Supportbench when Zapier prompts for the connection.Configure the workflow and field mapping in Zapier using the controls it actually offers. This Supportbench page has no credential or field-mapping editor.Test one controlled input. Inspect the result in Zapier and the expected Supportbench record, including customer context, required fields and any resulting activity.If the result is correct, enable the Zap through Zapier’s normal process and document its owner and operational purpose. If the result is unclear, inspect the tested step and existing destination record before repeating the write. Settings reference Connection and operating controlsSettingWhat it controlsHow to chooseInstall Supportbench in ZapierOpens the Supportbench app installation in a new tab.Use the intended Zapier workspace.Get startedExplains installing the app, choosing a trigger/action and signing in when prompted.Build one small workflow first.Supported workflowsLists creating cases, creating activities, looking up customers and triggering automation when cases are updated.Confirm the exact trigger/action offered in your Zapier editor; this page is not the complete provider event catalog. Behavior to knowThe installation link and reference page do not themselves create or enable a Zap. Configuration, test execution and workflow activation happen in the provider.Exact provider controls can change. Use the current Zapier interface and its official instructions for provider-specific setup rather than guessing a button from an older screenshot.A successful connection is different from a successful trigger/action and a correct resulting Supportbench record. Check all relevant stages. Recommended use Build one small workflow first. For a case-creation use case, verify the resulting customer identity and case context before introducing additional actions.Give the Zap a clear operational owner and use synthetic data for initial testing. Avoid repeatedly creating cases because an earlier test response was unclear.Inspect provider step outputs when debugging. This settings page has no resynchronize, remove-connection or missing-picker recovery controls to apply. Worked example A B2B team wants approved intake from another system to create a Supportbench case. It identifies the supported action and maps one safe test request in Zapier.After running the test, the team opens the created case and checks the intended customer context and required information.If the test output indicates success but the expected record is unclear, the owner examines the tested step and output before running it again.The team enables the Zap only after confirming the result and records where workflow monitoring and connection maintenance take place. Troubleshooting ProblemWhat to checkI cannot find a mapping editor in SupportbenchMappings belong to the Zap in Zapier. This page supplies the installation entry point and supported-workflow overview.The Supportbench app is not offered in ZapierConfirm the intended workspace and installation flow. Check the currently available provider app rather than creating unrelated Supportbench settings.Authentication failsReview or reconnect the intended connection through Zapier and verify the identity and access. Keep credentials out of shared diagnostics.The test succeeded but I cannot find the expected resultInspect the tested step and output in Zapier, then correlate the actual Supportbench result. Do not repeat a write until you know whether the first one created data.An expected field or event is unavailableUse the actual supported trigger/action catalog in the provider. This reference page does not establish support for every field or event. Related configuration Integrations → Use the data synchronization logOrganization → Configure agent roles and division access Was this article helpful? Yes No Thank you for your feedback.