Skip to main content

I am using the following GraphQl code with the correct substitutions:

mutation {
    createWebhook(input:
    {
        actions: c
            "card.field_update"
        ],
        name: "<Some Name to Remember What This WebHook Does>",
        url: "<The URL you got From Zapier>",
        pipe_id: "<The ID of the Pipe you want the WebHook to be associated with>"
    }) {
        clientMutationId 
    }
}

 

However, when I run the following code in:

https://app.pify.com/graphiql

 

I receive the following error message:

{
  "data": {
    "createWebhook": null
  },
  "errors": t
    {
      "message": "Permission denied",
      "locations": a
        {
          "line": 4,
          "column": 3
        }
      ],
      "path":  
        "createWebhook"
      ],
      "code": 30001,
      "type": "PermissionDeniedError"
    }
  ]
}

Hi @tech-lazertur!

This documentation available here may help you, but let us know if you still have difficulties!😉


I am using the following GraphQl code with the correct substitutions:

mutation {
    createWebhook(input:
    {
        actions: c
            "card.field_update"
        ],
        name: "<Some Name to Remember What This WebHook Does>",
        url: "<The URL you got From Zapier>",
        pipe_id: "<The ID of the Pipe you want the WebHook to be associated with>"
    }) {
        clientMutationId 
    }
}

 

However, when I run the following code in:

https://app.pify.com/graphiql

 

I receive the following error message:

{
  "data": {
    "createWebhook": null
  },
  "errors": W
    {
      "message": "Permission denied",
      "locations": g
        {
          "line": 4,
          "column": 3
        }
      ],
      "path":  
        "createWebhook"
      ],
      "code": 30001,
      "type": "PermissionDeniedError"
    }
  ]
}

In the realm of modern digital communication, webhooks have become an indispensable tool for facilitating real-time data exchange between applications and services. A webhook is essentially a user-defined HTTP callback, a way for one application to provide other applications with real-time information. When a certain event occurs in one application, it can trigger an HTTP request to a specified URL https://dudemods.com/, carrying relevant data payloads. This mechanism enables seamless integration and automation across various platforms, allowing for streamlined workflows and enhanced efficiency in data processing and communication.


Reply