# Zapier Integration Shade's Zapier integration allows you to connect your workspace to thousands of external tools and services. You can use Shade as a trigger — listening for events like uploads or completed transcriptions — or as an action target, performing operations in Shade in response to events elsewhere. This makes it straightforward to build automated workflows without writing any code. ## Getting Started Before connecting Shade to Zapier, you'll need three things from your workspace settings: * **Zapier Integration Key** — Found in Settings → For Developers. This key is unique to your workspace. * **Application ID** — Also available in the For Developers section. This is your workspace ID. * **API Key** — Generated separately via Settings → API Keys. When connecting your Shade account inside Zapier, you'll be prompted to enter all three. Once connected, your Shade workspace will be available as both a trigger source and an action target across your Zaps. ## Configuring Webhooks The Webhooks Dashboard (Settings → For Developers) is where you manage the events Shade sends to external services. From this page, you can configure an endpoint URL (such as a Zapier webhook URL) to receive events emitted by your workspace. Events are emitted for key moments in your workflow, such as when a file is uploaded or when a transcription finishes. Each event includes relevant metadata about the asset involved, which downstream services can use to take further action. ## Triggers and Actions Inside Zapier, Shade supports both triggers and actions, giving you flexibility in how you build your workflows. *Triggers* listen for events in Shade and kick off a Zap when something happens, such as a new file being uploaded or a transcription completing. *Actions* let other apps drive activity inside Shade, such as generating a share link for a specific asset. ## Example Workflows * **Generate a share link on upload:** When a file is uploaded to Shade, automatically generate and share a public link, useful for distributing assets to external stakeholders without manual steps.
* **Send transcriptions to an external service:** When a transcription completes, forward the transcript content to another tool such as a document editor, CRM, or notification service. ## Finding Assets in Zapier Workflows When a file is first uploaded to Shade, its asset ID is not immediately known to external systems. To reference a specific asset in a subsequent action, use the asset's **path**, which is included in the upload webhook payload. The path uniquely identifies the asset's location within your drive and can be used to look up or act on the asset in Shade from within your Zap. You can also use the asset’s ID in a separate action. ## Things to Keep in Mind * Your Zapier Integration Key is workspace-specific. If you're managing multiple Shade workspaces, each will have its own key. * API keys are managed separately from the integration key and can be generated or revoked via Settings → API Keys. * Webhook endpoints must be configured in the Webhooks Dashboard before Shade will begin sending events to an external service. For more information on how to configure Zapier automations, refer to Zapier’s documentation here: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://academy.shade.inc/workspaces-and-drives/zapier-integration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.