Metadocumentation
open-collective
open-collective
  • Welcome
  • About
    • Introduction
    • Terminology
    • Company
    • Pricing
    • Community Guidelines
    • Values
    • Team
    • Investors
    • Contributing
  • Product
    • Features
    • Roadmap
    • Comparison
    • User Profile
    • Currencies
    • Log-in System
  • Collectives
    • FAQ
    • Creating a Collective
    • Quick Start Guide
    • Customize Collective
    • Change Core Contributors
    • Tiers & Goals
    • Add Fiscal Host
    • Change Fiscal Host
    • Transparent Budget
    • Expense Policy
    • Approving Expenses
    • Updates & Comms
    • Events
    • Funding Options
    • Data Export
    • Buttons & Banners
    • Integrations
    • Zero Collective Balance
    • Closing a Collective
  • Financial Contributors
    • FAQ
    • Payments
    • Website Badge
    • Organizations
      • FAQ
      • Bulk Transfers
      • Gift Cards
      • Sustainer Resources
    • Collectives
      • Collective to Collective donations
  • Expenses & Getting Paid
    • FAQ
    • Submitting Expenses
    • Expense Comments
    • Edit an Expense
    • Tax Information
  • Fiscal Hosts
    • FAQ
    • Becoming a Fiscal Host
    • Create a Fiscal Host
    • Fiscal Host Settings
    • Invoices
    • Payouts
    • Host Dashboard
    • Add Funds Manually
    • Refunds
    • Host Fees
    • Local Tax Support
    • Agreement Templates
    • Open Source Collective
  • Contributing
    • Design
      • Design Workflow
      • Design Contribution Guidelines
    • Development
      • Contribution Guide
      • Best Practice Guidelines
      • Bounties
      • API
        • Members
        • Users / Emails
        • Collectives
        • Events
      • README Integration
      • Architecture
      • Postgres Database
      • PayPal
      • Post-Donation Redirect
      • Custom Tweets
      • Manual Reporting
      • Github Permissions
      • Translations
      • Testing with Cypress
      • Collective's locations
    • Documentation
      • Style guide
      • Suggesting changes
    • Translation
  • Internal
    • Scope
    • Team Retreats
    • Brussels Summer Team Retreat
    • Host Admin Manual
    • Newsletter
    • Support
    • Issue Labels
    • DNS Troubleshooting
    • Developer Guidelines
    • Architecture
    • Testing
    • Queries
      • Gift Cards
      • Transactions
      • Ops
      • Collectives
      • Hosts
      • Analytics
      • Emails
    • Projects
      • Maintainerati Berlin 2019
      • Season of Docs 2019
    • The Open Collective Way
      • Values
      • Community Guidelines
      • Core Contributors Guidelines
      • Core Contributors: Communication
      • Core Contributors: Expenses
      • Core contributors: Leave
      • Core Contributors: Compensation
Powered by GitBook
On this page
  • Zapier Integration
  • Twitter Integration
  • Chat Integrations
  • Slack Webhook
  • Gitter Webhook
  • For Admins
  1. Collectives

Integrations

PreviousButtons & BannersNextZero Collective Balance

Last updated 5 years ago

Zapier Integration

We now provide a Zapier App! Zapier should be the default choice whenever you need to integrate Open Collective with a third party service. All you need is:

  • To create an API key on

  • To add the app on

Like everything we do, our Zapier app is open source (MIT). If you need an action that's not yet on the Zapier app and feel ready to work on the integration: check

Otherwise feel free to open an issue on to ask for it. Please tell us about our use case, we love to understand why our users do what they do!

Twitter Integration

Connect your Twitter to automatically thank new backers who contribute to your Collective.

Go to "edit Collective" > "Connected Accounts" and click the "Connect Twitter" button.

Chat Integrations

Slack Webhook

  • In Slack, select menu Apps & Integrations

  • Click Build Your Own > Make a Custom Integration > Incoming WebHooks

  • Choose a channel, or create a new channel, where the notifications will be sent

  • Click Add Incoming WebHooks Integration

Gitter Webhook

  • Go to your room's integrations and click Open Collective

  • Copy the provided Webhook URL and click Done

For Admins

The webhook can be added in the database Notifications table:

INSERT INTO "Notifications" (
  "GroupId",
  channel,
  type,
  active,
  "webhookUrl")
VALUES ((SELECT id from "Groups" where slug = '<group slug>'),
        '<channel: either slack or gitter',
        '<type: see note below>',
        true,
        '<webhook URL>');

type (would actually be more properly named activity) can be:

  • either 'all' (*) to send notifications for all activities (group transaction created, payment received from Stripe, etc)

You can set up Open Collective notifications in your Slack or Gitter channel. First set up a webhook, described below, and then and we'll add the hook to our platform.

or some constant from to only send notifications for a specific activity

are not linked to any group and will therefore be ignored.

send it to us
here
Some activities
http://opencollective.com/applications
https://zapier.com/developer/public-invite/21484/63399c65bb01d75e00fe091ae7f58683/
https://github.com/opencollective/opencollective-zapier/settings
https://github.com/opencollective/opencollective/issues