Web2 Plugins (Zapier)
GitHub Commits

Mint NFTs from GitHub Commits

In this tutorial, we'll setup a no-code automation using the Owl Zapier App (opens in a new tab) to mint an NFT whenever someone makes a commit to your Github repository

Prerequisites

Before you begin you should have the following

Steps

Zapier Template

Create a Zap using our one-click template (opens in a new tab) for Github Commits & Owl Protocol Zaps. You will now configure your Zap from within the Zapier Editor

start

Configure the Github Trigger

⚠️

Every contributor must enable their email in Github to receive the NFT. This is usually enabled by default, but we recommend this Github guide (opens in a new tab) for more info on commit email addresses.

Click on New Commit in Github box to configure the Zap Trigger.

  • Account: Connect your Github Account with Zapier
  • App & Event: Set the Event to "New Commit"
  • Trigger: Select the Github repository you created (Click "+ Load More" if you can't find it)
  • Test: The Zap Trigger should have collected the initial commit with your email as "Committer Email" (see Prerequisites)
trigger

Configure the Owl Protocol Action

💡

To use Zapier with multiple Owl Protocol projects, you can connect new accounts to Zapier using each project's API Key. You can also rename connections to match your project name to easily identify them.

Click on Mint ERC721 in Owl Protocol box to configure the Zap Action.

  • Account: Connect your Owl Protocol Account with Zapier by pasting your API Key
  • App & Event: Set the Event to "Mint ERC721"
  • Action: Configure the action parameters
    • Collection Address: If you have already deployed a collection, you will see the names and addresses of these collections in the dropdown. If not, first deploy a collection.
    • To: Use the Committer Email output from the Github Commit. This way, NFTs will be sent to anyone who contributes to your repository.
    • Token Template ID (optional): If you have previously created Templates, they will appear in the dropdown. If not, you can skip this.
    • Name (optional)
    • Description (optional)
    • Image (optional)
    • Attributes (optional)
  • Test: The Github Commit Trigger should have passed down the sample submission, and testing the Owl Action should mint a new ERC721 successfully
action

Publish your Zap

After testing the Zap, publish your Zap. While it is on, it will mint an ERC721 from the selected collection for every new commit made to your repository's default branch.

success

Workflow Recap

By following this guide, you have successfully set up an automated workflow that mints NFTs whenever someone completes contributes to your Github repository. This integration saves time and ensures immediate reward distribution, enhancing user engagement and automating the NFT minting process.

Additional Tips

  • Troubleshooting: If your Github commits are not triggering the Zap, double-check that your Gihtub Zapier connection and that Committer have their email enabled.
  • Customization: Fill in fields such as name, image, and attributes to personalize the NFTs. You can also create Token Templates in the Owl Protocol Dashboard to further customize the NFTs to meet your specific needs.

Next Steps

Explore the wide range of apps available on Zapier and experiment with Owl Protocol. Develop your own workflows to meet your specific needs, and discover creative ways to automate and enhance your Web3 experience.