Skip to main content
Zapier is a tool for automating repetitive tasks between two or more apps—no code is necessary. Disco has a Zapier app that can trigger actions in other systems connected to Zapier. Integrations Zapier The core use case for Zapier using with Disco is adding users to a Academy or Programbased on a Trigger in Zapier.
Zaps in Zapier use older terminology. In Zapier, Community refers to what Disco now calls an Academy, and Product refers to what Disco now calls a Program. Keep this in mind when configuring zaps from Zapier.

​
How It Works

The Disco Zapier app has both triggers and actions available. A trigger is used to start a workflow (Zap) in Zapier, and an action is a step in a workflow (Zap) that can use the data from a trigger to perform a specific action in that integration.  When connecting Disco and Zapier, you will create a connection for each Academy.

​
Triggers available in Zapier:

  1. Product-specific (need to select an available product when creating the zap)
    • User joined product
    • User left product
    • User applied to product
    • Product curriculum section started
    • Product event date/time changed
    • Product post published
    • User submitted assignment
    • User deleted assignment submission
    • User completed a curriculum module in a product
  2. Pathway-specific (need to select an available pathway when creating the zap)
    • Pathway added
    • Pathway updated
    • Pathway deleted
    • User joined pathway
    • User left pathway
    • User completed pathway
  3. Event-specific (need to select an available event when creating the zap)
    • User joined event (specific event)
    • User left event (specific event)
  4. Global (no filter on product/pathway/event)
    • User joined any event in the community
    • User completes community onboarding
  •  

​
Example Actions available in Zapier:

  • Add user to Community
  • Add user to a Product (i.e. course) *Note: adding a user to a Product will also add them to the Community
  • Remove user from Community
  • Remove user from a Product
  • Fetch User Profile (this outputs the Profile Fields for use in other Zap actions)
  • Invite user to a pathway
  • Add user to a pathway
  • Remove user from a pathway
Email addresses are required for the above actions, but first and last names are optional. Once added to a Product/Community, the Member will receive the regular emails that automatically come from Disco.

​
How To Connect Zapier

  1. Navigate to Admin > Integrations > Connect Zapier.
  2. Click Generate Zapier API Key.
  3. Copy the generated key.
  4. When connecting Disco in Zapier for the first time, you will be asked for this API key. NOTE: Because the API key is community-specific, do not use an existing API key you may have from another community you run on Disco.
  5. See Disco’s Zapier page for more details and where you can search over 5000+ apps to connect with.

​
Important Considerations

  • When using Zapier to integrate with Disco, it’s important to understand that Zapier connects inputs and outputs from various sources, which can lead to variability in how these connections function. You’ll need to ensure that you fully understand the outputs from your triggers and how to map them correctly to Disco actions within your Zaps. Since we do not have visibility into the specific configurations of your Zaps, our support is limited to making sure that the Disco integration operates as expected.
  • The test data for triggers is currently static. When the Zap is published and enabled, and then the trigger fires, the real user data will be sent. 

​