Close menu
Explore Plans
Mobile menu Close menu
Back

GitHub to Zubie integrations

Automate your workflows between GitHub and Zubie with IFTTT.

Create your own GitHub and Zubie workflow

Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.

43 triggers, queries, and actions

Any new closed issue

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time any issue is closed in a repository you own or collaborate on.

Any new commit

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time a new commit in a repo is created on Github.

Any new Gist

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you create a new Gist on Github.

Any new issue

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time any new issue is opened in a repository you own or collaborate on.

Any new notification

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time you receive a new notification on Github.

Any new notification from a repository

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you receive a new notification from a specific repository on Github.

Any new release

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time a repo release a new version on Github.

Any new repository event

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time a new event occurs in a repository.

Check engine light is on for any vehicle

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires when ANY vehicle's Check Engine light has been activated, caused by a Diagnostic Trouble Code (DTC).

Hard acceleration detected

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
Triggers when your vehicle has a hard-acceleration event.

Hard braking detected

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
Triggers when a vehicle detects a hard brake event.

High speed driving detected

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
Triggers when your vehicle is driven at speeds above a safe level (configured within Zubie).

History of closed issues

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time any issue is closed in a repository you own or collaborate on.

History of instances a vehicle left a place

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of instances when a vehicle left a place.

History of issues

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time any new issue is opened in a repository you own or collaborate on.

History of issues assigned to you

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time a new issue is assigned to you.

History of pull requests for a specific repository

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time a new pull request is opened for a repository you specify.

History of repositories by a specific username or organization

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of every time a new repository is created by the username or organization you specify.

History of trip ends

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of the end of every vehicle trip, as indicated by the Ignition being turned off.

History of vehicle arriving at a place

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when a vehicle arrived at a specific place such as Home or Work (defined within Zubie).

History of vehicle driven between hours

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when a vehicle trip ends during a selected time frame.

History of vehicle out of range

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when your vehicle was further than an allowed distance from a specified location.

History of when Check engine light was on for any vehicle

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when ANY vehicle's Check Engine light was been activated, caused by a Diagnostic Trouble Code (DTC).

History of when hard acceleration was detected

Pro plus icon
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when your vehicle was a hard-acceleration event.

Create an issue

Pro icon
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will create a new issue for the repository you specify.

Create an issue/pull request comment

Pro icon
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will comment in a specific issue or pull request on Github.

Create new Gist

Pro icon
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will create a Gist for you.

Any new closed issue

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time any issue is closed in a repository you own or collaborate on.

Any new commit

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time a new commit in a repo is created on Github.

Any new Gist

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you create a new Gist on Github.

Any new issue

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time any new issue is opened in a repository you own or collaborate on.

Any new notification

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time you receive a new notification on Github.

Any new notification from a repository

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you receive a new notification from a specific repository on Github.

Any new release

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time a repo release a new version on Github.

Any new repository event

Pro icon
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time a new event occurs in a repository.

Check engine light is on for any vehicle

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires when ANY vehicle's Check Engine light has been activated, caused by a Diagnostic Trouble Code (DTC).

Create an issue

Pro icon
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will create a new issue for the repository you specify.

Create an issue/pull request comment

Pro icon
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will comment in a specific issue or pull request on Github.

Create new Gist

Pro icon
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will create a Gist for you.

Build an automation in seconds!

You can add delays, queries, and more actions in the next step!

GET STARTED

How to connect to a GitHub automation

Find an automation using GitHub

Find an automation to connect to, or create your own!

Connect IFTTT to your GitHub account

Securely connect the Applet services to your respective accounts.

Finalize and customize your Applet

Review trigger and action settings, and click connect. Simple as that!
Get started

Upgrade your automations with

Start your free trial

More on GitHub and Zubie

About GitHub

GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Turn on Applets to automatically track issues, pull requests, repositories, and to quickly create issues.

Connect GitHub

More integrations with GitHub

About Zubie

Zubie is a connected car service that makes driving safer, easier and less expensive. It tracks your trips, alerts you to engine and battery problems, unsafe driving events, arrivals and departures, and more.

Connect Zubie

More integrations with Zubie