I agree that having the old value as part of the data in this webhook would make it much more useful. (Also for my use case.)

@skw or @omerbensaadon are there any thoughts on sending the previous state as part of the webhook body?

@MPLew-is I think that would be a great idea! Not our highest priority at the moment but if anyone else agrees, please chime in

I am trying to integrate with Jira, so I have limited control available and it is not easy to make a response web hook call. I want to simply know when an issue is transitioned between todo and in progress so I can update the associated Jira ticket's status.

Currently, I just get told:

 "changes": {
    "field_value": {
      "field_node_id": "PVTF_ABCDEF0123456789",
      "field_type": "single_select"
    }
  }

It would be great if it instead sent:

 "changes": {
    "field_value": {
      "field_node_id": "PVTF_ABCDEF0123456789",
      "field_name": "Status"
      "old_value": "todo",
      "new_value": "In Progress"
    }
  }

👋 See the comment below and check out this week's changelog which includes this information on the previous and current field value ✨

Agreed. This feels like a big omission. Part of what's cool about GH Projects is the ability to automate everything.

Hey folks, wanted to call out that we won't be able to do this for a bit and it has to do with how Projects are Org level and Actions are Repo level.

Simply put, we don't have an elegant way to bridge the gaps between Orgs and Repos in this regard.

As @MPLew-is was mentioning, rerouting the webhook to your own infra is the work around for now. We have conversations open with the Actions team but that isn't our backlog so hard to tell when something like this will be supported.

It will be one day, just don't have a ton of clarity on when. Apologies in advance, I totally agree that this is a big omission.

Since project items can be PRs, could we add actions triggers for adding / removing a pr to/from a project? Or add it to the PR edit trigger?

Has this changed in the meantime? I wasn't able to subscribe to project v2 item changes in the action

How is this still not a thing 18 months later? With classic Projects being disabled, this breaks any ability for GitHub users to have a meaningful SDLC with automation managed within the platform. At least re-enabled Classic projects until you can meet parity.

Hey @eelco, sincerely appreciate your feedback, its been a gift!

There’s a release coming sometime next week that should begin leveraging the newer version of the GraphQL API which may resolve some of your concerns?

Hang tight, I’ll update you in this thread when it has been released

Is it out yet? 😇

Hey sorry @eelco, been on a rather long vacation, I'll ask today!

hey! this should be released! Can you let me know if it looks good from your end?

Hi @omerbensaadon, using the new API (not available through the GraphQL explorer, because it’s missing the read:project scope?) I’m able to query the field values with the PVT…_ ids, but there are still fields missing. E.g. if I do

{
  node(id: $node_id) {
    ... on ProjectV2Item {
      fieldValues(first: 10) {
        nodes {
          __typename
        }
      }
   }
}

I will get 9 fields back, but there are more in my project and the one I’m looking for (with the ProjectV2ItemFieldDateValue type) is missing. Using the fieldValueByName API I can get the value of the field I’m looking for, but I’d rather use an ID because it’s stable.

Apologies if unclear, but I'm looking to go the other way in translating: given a PVTSSF_... node ID, is there a way to get the corresponding PVTF_... node ID? I'd like to configure my automation using the PVTSSF_... ID, and have it be able to use that to match against the PVTF_... node ID coming in via the webhook.

I've been using projectV2 queries the entire time, so I'm not affected by that.

👋 @MPLew-is Ah I see what happening I think the issue is that PVTF... is for ProjectV2Field types and PVTSSF_... is used for fieds like ProjectV2SingleSelectField.

I don't think there's a way to get the corresponding ProjectV2Field from a ProjectV2SingleSelectField node id but it strikes me that we should probably be sending the ProjectV2SingleSelectField/PVTSSF_... in the webhook payload. I'm going to create an internal issue so that we can look into this further.

👋 Some good news, I'm shipping a fix for this soon that updates the node id types, this will affect single select and iteration fields. I'll confirm when this has been deployed.

Looks like this has shipped given that my automations broke in the last few hours 😅 Nothing a field ID configuration update didn't take care of, thanks for getting that out!

@MPLew-is Yes sorry, I forgot to confirm, it did deploy 👍 Let me know if anything else comes up 👌

👋 @PsychoPast Thanks for reaching out, I took a look and their docs don't specify which events they support.

Looking at my outgoing deliveries everything seems fine from our end as we get 204 responses from events that show messages in channels and ones that don't:

I did confirm that it's not just project_v2 webhooks that aren't showing up, I haven't gone through every webhook but I tested labels which also don't post to channels.

Have you reached out to discord yet? They might be able to fix their integration and/or let you know which events they specifically support.

I can check internally if we've collaborated with them on webhooks in the past.

👋 @PsychoPast Thanks for reaching out, I took a look and their docs don't specify which events they support.

Looking at my outgoing deliveries everything seems fine from our end as we get 204 responses from events that show messages in channels and ones that don't:

I did confirm that it's not just project_v2 webhooks that aren't showing up, I haven't gone through every webhook but I tested labels which also don't post to channels.

Have you reached out to discord yet? They might be able to fix their integration and/or let you know which events they specifically support.

I can check internally if we've collaborated with them on webhooks in the past.

Hey! Thanks for taking a look at the issue.

That is indeed weird. I also was getting 204 responses from project_v2 webhooks triggers but I thought that the problem lied in the response. A malformed field or something.
I didn't test all the webhooks but all of them I tried did work and I assumed that it was an issue affecting only project_v2.

And no I haven't reached to Discord. I'm doubt that they would be helpful in any way.

I'm not familiar about this matter but given the fact we append "/github" at the end of discord webhook urls when setting up a github repo webhook, doesn't that mean that you indeed have collaborated on webhooks with them to make webhook integration into their app work smoothly?

Best regards :)

I believe it's just something Discord has set up to parse manually to have pretty messages, they did it for Slack too. I think you'll have to wait for Discord to add support for this event.

https://discord.com/developers/docs/resources/webhook#execute-githubcompatible-webhook

Things like this are one reason I’d love to see the decision to only use GraphQL reconsidered - in order for Discord to generate messages from webhooks with any helpful content, they’re now going to have to set up a GitHub App installation in order to have the right credentials to go query project item information.

If the webhook bodies contained a little more information in them than just GraphQL node IDs, integration with external services could be done a lot more simply. I don’t doubt Discord has the resources to implement it fairly quickly if they wanted, but that’s quite a bit of start-up overhead if you’re building something custom like I did.

Hi, I've encountered the similar issues with GitHub Projects webhooks not triggering Discord notifications, and I believe this is a problem on the GitHub side. When making changes in GitHub Projects, such as moving an item from one column to another or creating a new column, there is no delivery recorded in the Recent Deliveries history of the webhooks management panel.

In contrast, GitHub Repo webhooks are delivered normally to Discord. However, it appears that Discord side does not properly process all of these webhooks, like the delivered label changes webhooks cannot trigger the notification in Discord...

Should be fixed now 👍

Look out for that space! Jump! Fast

When you input the webhook URL into github, make sure you paste it in and then add /github on the end of the URL for Discord to be able to read it.

When you input the webhook URL into github, make sure you paste it in and then add /github on the end of the URL for Discord to be able to read it.

I know that info! Working others but not working projects to discord. 😭 (Thanks)

Strange... Sorry, I don't think I can really help you with that...

I think you need to create the app under an organization, since that's what Projects are tied to:

Sorry forgot to come back.

Thank you @MPLew-is, this was the problem.

Hi there! 👋
Thanks for the thread, I've been struggling to work with the api and a Github App and it helped me a lot!

But still, there's something I don't quite get... Projects can also be tied to users on Github, right?
I was able to create a project V2 in my personal account (authenticated as myself, not an App), also I linked it , but I want to be able to create a project tied to users' accounts (or to some users' repo, that would be ok too), where the App is previously installed. Is there a way to do that? Am I misunderstanding how projects V2 work?

let me share what I was trying to pull off:

 mutation{
   createProjectV2(input: {
     title:"V2 project related to test repo"
     ownerId:"MDQ6VXNlcjgwNTM2MDY2" # my own ownerId
     repositoryId:"R_kgDOI5E_Zg" # the dummy repo Id that I created to test this functionality
   }){
     __typename
     projectV2{
       title
       id
       creator {
         login
         __typename
         resourcePath
       }
     }
   }
 }

I don't know where to get an authentication method equivalent to the access token (classic) that I got from my personal account.
Can someone point me into the direction of how to get the authentication for running this mutation with a GH App? Thanks in advance!

Not that I can tell at this time - I configure all my webhooks to filter based on a project's GraphQL ID, but still receive everything under an organization.

Wish we could just trigger custom workflows.

It's a little more built to trigger Slack notifications, but I built an AWS Lambda function for this here: https://github.com/MPLew-is/github-projects-webhook-receiver

Might at least be a decent starting point, or I’m happy to carve off some pieces so they can be used separately.

Not at the moment, we would likely have to introduce user webhooks. Are you planning to write a integration to work with user-owned projects?

It seems like a major oversight that there is no possible way to trigger anything when something on a project updates for projects tied to a user account. The only way to check if something has changed is to poll the GraphQL API. Will there ever be a webhook for project v2 updates tied to user accounts?

👋 Hi @FPEekgoodX I've pitched these changes, the prioritization for this work is still under review, will let you know once it gets scheduled.

@FPEekgoodX see the comment below and check out this week's changelog which includes this support ✨

👋 @paragon-cloud is this for a GitHubApp?

@rmusick2000 The GitHub App support for porjects_v2 finally landed, sorry for the delay (it was unfortunately out of my control).

@skw Thank you! I am able to see the basic notifications now for projects_v2. Still can't see link/unlink, but that is consistent with the documentation.

@skw for the second part of the original question, "Nor can I send events for editing, adding or deleting options in the Status field for a ProjectsV2", is there a way to send these notifications? I thought they might be included in the edit notices for a projects_v2.

More generally, I can't seem to send notifications for any mod to any projects_v2 field. Since fields (like Status, or user-defined fields) are used as columns in the project views, being aware of changes to them matter.

One option is to continuously poll for the current fields in the ProjectV2View of every project, but this seems expensive. Is there a better choice?

More generally, I can't seem to send notifications for any mod to any projects_v2 field. Since fields (like Status, or user-defined fields) are used as columns in the project views, being aware of changes to them matter.

Hi @rmusick2000 we do have an issue to implement project_v2_field actions which would allow you to get updates for field changes. Unfortunately that work isn't prioritized atm so it would depend on when I have some spare time to implement it.

One option is to continuously poll for the current fields in the ProjectV2View of every project, but this seems expensive. Is there a better choice?

Hmmm ya that does sound expensive, under what circumstances do you need to update fields? Potentially you could only update fields when items are updated? and/or limit the polling

Hi @skw, yes, we can and will limit the polling as you suggest. It does increase latency, unfortunately, by adding 1 more round trip to GitHub for several common operations. Please add one vote for increasing the priority of the push notification, and thanks (again) for your answers!

Hi @danielbrodin, currently we only return the graphql node_id, which allows you to make a query and get all the fields you need. We would like to eventually add support for changed values but this wouldn't include all other field values.

A query to get all fields could look something like this (would need to add the fieldValue types you need):

{
  node(id: "PVTI_...") {
    ... on ProjectV2Item {
      fieldValues(first: 1) {
        nodes{                
          ... on ProjectV2ItemFieldTextValue {
            text
            field {
              ... on ProjectV2FieldCommon {
                name
              }
            }
          }
        }              
      }
    }
  }
}

See the comment below and check out this week's changelog which includes this support ✨

See the comment below and check out this week's changelog which includes this support ✨

Found the solution myself.
Interestingly enough, I was banging with the node "changes.field_value.field_node_id", and it doesn't contain changes, it contains only all options (columns). The changes (not changes but current final state of a card and its column location) are in another node projects_v2_item.
The solution for anyone interested:

// this is javascript by the way
async function getData() {
const token = "ghp_X*************************************";
const apiUrl = https://api.github.com/graphql;

// ids coming from webhook request to your api, but they are not necessarily tied to a webhook event
const projectsV2ItemNodeId = "PVTI_l*****************************";
const changesFieldValueFieldNodeId = "PVTSSF_lA*************************";

const requestBody = {
query: { nodes(ids: ["${projectsV2ItemNodeId}", "${changesFieldValueFieldNodeId}"]) { ... on ProjectV2Item { fieldValues(first: 8) { nodes { ... on ProjectV2ItemFieldSingleSelectValue { optionId } ... on ProjectV2ItemFieldTextValue { text field { ... on ProjectV2FieldCommon { name } } } } } } ... on ProjectV2SingleSelectField { options { id name } } } } ,
};

try {
const response = await fetch(apiUrl, {
method: "POST",
headers: {
Authorization: Bearer ${token},
"Content-Type": "application/json",
},
body: JSON.stringify(requestBody),
});

if (response.ok) {
  const data = await response.json();
  const nodes = data.data.nodes;
  const fieldValues = nodes[0].fieldValues.nodes;
  const cardName = fieldValues[0].text;
  const optionId = fieldValues[1].optionId;
  const options = nodes[1].options;
  const selectedOption = options.find((item) => item.id === optionId);
  console.log("selectedOption", selectedOption.name);
  console.log("cardName", cardName);
} else {
  throw new Error("Failed");
}

} catch (error) {
console.error("Error:", error);
}
}

getData();

Sorry for the late reply, org admins should have access to these hooks, or permissions can be requested via a GitHub App installtion.

I suppose you could trigger a workflow manually, which might be the only workaround I can think of at the moment. We've been discussing projects actions internally but haven't planned any work just yet.

If using workflow then it'll be 1 way synchronization from repo -> project 🤔

Then to synchronize projects -> repo, I guess we need to run the workflow manually? 🤔

That's great news, and I've already started relying on this for migrating my application to GitHub Projects v2. However, I discovered that when a milestone is changed, this webhook is also triggered, but doesn't contain the "from" and "to" objects. Furthermore, the provided node_id is almost useless because querying the GraphQL API doesn't give more information (we cannot retrieve the milestone name, description, or even its node_id, as the provided node_id is of ProjectV2Field type). So it would be great if the "from" and "to" values could be added to the webhooks, and some more information (e.g., the milestone node_id) could be added to the GraphQL API for this type of node.

Thank you for this feedback and for sharing your current workaround, we have this request logged on our end. This is not currently supported given projects live at the organization level rather than repository level where events that trigger workflows live, so we'd need to implement organization-level actions.

We will keep you updated on any plans for this 👍