Connect GitHub and Context.dev to Build Intelligent Automations

Choose a Trigger

GitHub

When this happens...

Choose an Action

Context.dev

Automatically do this!

Ready to use GitHub and Context.dev automations

Actions and Triggers

When this happensTriggers

A trigger is an event that starts a workflow.

New Issue Created

New Issue Created

Runs when a new issue is created.

New Branch or Tag Created

New Branch or Tag Created

Runs when a new branch or tag is created.

New Release Published

New Release Published

Runs when a new release is published in the selected repository.

Pull Request Opens or Closes

Pull Request Opens or Closes

Runs when PR opens or closes

New Comment Added to Issue

New Comment Added to Issue

Runs when a new comment is added to an issue.

Repository Forked

Repository Forked

Runs when a repository is forked.

Do thisActions

Action is the task that follows automatically within your GitHub integrations.

Create Issue

Create Issue

Creates a new issue in a specified repository.

Find Repository

Find Repository

Return repository details for a specified GitHub user or organization and repository name.

Get Pull Requests Details

Get Pull Requests Details

fetches details of a specific Pull Request from GitHub.

Update GitHub Issue

Update GitHub Issue

Modify an existing issue's title, description, state, assignees, labels, or milestone in a GitHub repository.

Find Issue

Find Issue

Finds an issue in a repository by number or by title and state.

Find Organization

Find Organization

Finds an organization by name.

Need help building your workflow?

Get instant answers from our AI assistant or connect with a support specialist anytime.

Frequently Asked Questions

How do I start an integration between GitHub and Context.dev?

To start, connect both your GitHub and Context.dev accounts to viaSocket. Once connected, you can set up a workflow where an event in GitHub triggers actions in Context.dev (or vice versa).

Can we customize how data from GitHub is recorded in Context.dev?

Absolutely. You can customize how GitHub data is recorded in Context.dev. This includes choosing which data fields go into which fields of Context.dev, setting up custom formats, and filtering out unwanted information.

How often does the data sync between GitHub and Context.dev?

The data sync between GitHub and Context.dev typically happens in real-time through instant triggers. And a maximum of 15 minutes in case of a scheduled trigger.

Can I filter or transform data before sending it from GitHub to Context.dev?

Yes, viaSocket allows you to add custom logic or use built-in filters to modify data according to your needs.

Is it possible to add conditions to the integration between GitHub and Context.dev?

Yes, you can set conditional logic to control the flow of data between GitHub and Context.dev. For instance, you can specify that data should only be sent if certain conditions are met, or you can create if/else statements to manage different outcomes.

GitHub

About GitHub

GitHub is a platform for version control and collaboration, allowing developers to work together on projects from anywhere. It provides tools for code review, project management, and continuous integration.

Learn More
Context.dev

About Context.dev

context.dev is a comprehensive platform designed to enhance and manage your brand's online presence. It offers tools for brand development, digital marketing, and analytics to help businesses grow and maintain a strong brand identity.

Learn More