Close menu
Explore Plans
Mobile menu Close menu

Camio to GitHub integrations

Automate your workflows between Camio and GitHub with IFTTT.

Create your own Camio and GitHub 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.

32 triggers, queries, and actions

Advanced motion 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.
This Trigger fires when advanced motion is detected (based on the specified criteria).

Any new closed issue

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

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

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

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

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

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

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

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.

Motion 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.
This Trigger fires when motion is detected (based on the specified criteria).

New issue assigned to you

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 issue is assigned to you.

New pull request for a specific repository

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 pull request is opened for a repository you specify.

History of Camera Power disconnected

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 power was disconnected for any of your cameras that use the Camio App (or for a specific camera only). It only includes disconnects when you've been recording for at least 10 minutes and has a max entry of one per 24 hour

History of closed issues

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 issues

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

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

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

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.

List Gists.

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 Gists owned by the current user.

List starred Gists

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 Gists starred by the current user.

List starred repos

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 repositories starred by the current user.

List watched repos

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 repositories watched by the current user.

Lists users that have starred the repository

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 users that have starred the repository.

Create an issue

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

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

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.

Start recording

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 starts recording on one or all of your cameras.

Stop recording

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 stops recording on one or all of your cameras.

Turn off motion notifications

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 turns off all motion notifications for all your cameras from your Camio App.

Turn on motion notifications

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 turns on all motion notifications for all your cameras from your Camio App.

Advanced motion 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.
This Trigger fires when advanced motion is detected (based on the specified criteria).

Any new closed issue

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

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

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

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

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

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

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

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.

Create an issue

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

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

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 Camio automation

Find an automation using Camio

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

Connect IFTTT to your Camio 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 Camio and GitHub

About Camio

See what's happening while you are away. Turn any device into a smart home monitoring camera with Camio.

Connect Camio

More integrations with Camio

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