How to sync GitHub issues to Jira with Pipedream

pipedream.com > New > Workflow

Create new Pipedream workflow

Go to pipedream.com and click New in the top navigation. Select Workflow from the dropdown menu. You'll see an empty workflow canvas with a placeholder trigger step. This is where you'll configure the GitHub webhook that fires when issues are created.

1. 1Click 'New' in the top navigation bar
2. 2Select 'Workflow' from the dropdown
3. 3Click on the default trigger step to configure it

Trigger Step > Search Apps > GitHub > New Issue (Instant)

Configure GitHub webhook trigger

Click the trigger step and search for GitHub in the app list. Select 'New Issue (Instant)' as your trigger type. This creates a webhook that GitHub will call immediately when issues are created. You'll see a unique webhook URL generated automatically.

1. 1Search for 'GitHub' in the app selector
2. 2Choose 'New Issue (Instant)' trigger
3. 3Copy the generated webhook URL for the next step

GitHub Trigger > Connect Account

Connect GitHub account

Click 'Connect Account' in the GitHub trigger step. A popup will open asking for GitHub permissions. Grant access to the repositories where you want issue sync enabled. Pipedream needs read access to issues and repository metadata to process the webhook data.

1. 1Click 'Connect Account' button
2. 2Authorize Pipedream in the GitHub popup
3. 3Select which repositories to grant access to
4. 4Click 'Install & Authorize'

GitHub Repo > Settings > Webhooks > Add webhook

Add GitHub webhook in repository

Go to your GitHub repository settings and navigate to Webhooks. Click Add webhook and paste the Pipedream URL. Set Content type to 'application/json' and select 'Let me select individual events'. Check only the 'Issues' event box since we don't want other events triggering this workflow.

1. 1Go to your GitHub repository settings
2. 2Click 'Webhooks' in the left sidebar
3. 3Click 'Add webhook' button
4. 4Paste the Pipedream webhook URL in Payload URL
5. 5Set Content type to 'application/json'
6. 6Select 'Let me select individual events'
7. 7Check only 'Issues' event

GitHub Repo > New Issue, then Pipedream Workflow > Trigger Step

Test GitHub trigger

Create a test issue in your GitHub repository with a title, description, and assignee. Go back to Pipedream and check the trigger step for incoming data. You should see the full issue payload including title, body, labels array, and assignee object within 5-10 seconds.

1. 1Create a new issue in your GitHub repository
2. 2Add a title, description, assign it to someone
3. 3Go back to Pipedream workflow
4. 4Check the trigger step for the test data

Workflow > + Add Step > Jira > Create Issue

Add Jira action step

Click the + button below your trigger to add a new step. Search for Jira and select 'Create Issue' action. This step will receive the GitHub issue data and create a corresponding Jira ticket. The step will appear connected to your trigger with a flow arrow.

1. 1Click the + button below the GitHub trigger
2. 2Search for 'Jira' in the app list
3. 3Select 'Create Issue' action
4. 4The step appears below your trigger

Jira Step > Connect Account

Connect Jira account

Click 'Connect Account' in the Jira step. Enter your Jira site URL (like company.atlassian.net), email, and API token. You'll need to generate an API token from your Jira account settings first. Pipedream will test the connection and show your available projects.

1. 1Click 'Connect Account' in the Jira step
2. 2Enter your Jira site URL (company.atlassian.net)
3. 3Enter your email address
4. 4Paste your Jira API token
5. 5Click 'Connect'

Jira Step > Project > Issue Type > Field Mapping

Configure Jira field mapping

Select your target Jira project and issue type (usually Bug or Task). Map the GitHub issue title to Jira summary field. Map GitHub body to Jira description. For assignee, you'll need to map GitHub usernames to Jira account IDs since they're different systems.

1. 1Select your Jira project from dropdown
2. 2Choose issue type (Bug, Task, etc)
3. 3Map Summary to GitHub issue title
4. 4Map Description to GitHub issue body
5. 5Configure assignee mapping if needed

Between Steps > + > Code > Node.js

Add label transformation code

Click + to add a Node.js code step between GitHub and Jira. This step will convert GitHub labels array to Jira-compatible format. GitHub sends labels as objects with name/color, but Jira expects simple strings or specific label IDs depending on your setup.

1. 1Click + between GitHub and Jira steps
2. 2Select 'Code' then 'Run Node.js'
3. 3Name the step 'Transform Labels'
4. 4Add the label conversion code

This code step transforms GitHub labels and handles assignee mapping between the two systems. Paste it in a Node.js code step between your GitHub trigger and Jira action.

export default defineComponent({
  async run({ steps, $ }) {
    const issue = steps.trigger.event;

export default defineComponent({
  async run({ steps, $ }) {
    const issue = steps.trigger.event;
    
    // Map GitHub usernames to Jira account IDs
    const userMap = {
      'sarah-dev': '5d2a8b0c1f2a3b4c5d6e7f8g',
      'mike-frontend': '1a2b3c4d5e6f7g8h9i0j1k2l',
      'alex-backend': '9z8y7x6w5v4u3t2s1r0q9p8o'
    };
    
    // Convert GitHub labels to Jira format
    const jiraLabels = issue.labels
      .map(label => label.name)
      .filter(name => !['wontfix', 'duplicate'].includes(name))
      .slice(0, 5); // Jira has label limits
    
    // Set priority based on labels
    let priority = 'Medium';
    if (issue.labels.some(l => l.name.includes('urgent') || l.name.includes('critical'))) {
      priority = 'Highest';
    } else if (issue.labels.some(l => l.name.includes('high'))) {
      priority = 'High';
    }
    
    // Map assignee if exists
    const assigneeId = issue.assignee ? userMap[issue.assignee.login] : null;
    
    return {
      summary: issue.title,
      description: `*From GitHub Issue #${issue.number}*\n\n${issue.body}\n\n[View on GitHub](${issue.html_url})`,
      labels: jiraLabels,
      priority: priority,
      assignee: assigneeId,
      githubUrl: issue.html_url,
      githubNumber: issue.number
    };
  }
});

GitHub Repo > New Issue, then Pipedream Workflow > Step Results

Test complete workflow

Create another test GitHub issue and watch the workflow execute. Check each step's output data to verify the transformation is working correctly. The final Jira step should show the created ticket ID and URL. Verify in Jira that the ticket appears with correct title, description, and labels.

1. 1Create a new test issue in GitHub
2. 2Watch workflow execution in Pipedream
3. 3Check each step's output data
4. 4Verify the Jira ticket was created correctly
5. 5Check ticket details in Jira interface