@sergio-eliot-rodriguez
I couldn't test the send-message-to-contact action because I got the following error

{
  "type": "error.list",
  "request_id": "0045u65gk3nlgf7v27g0",
  "errors": [
    {
      "code": "api_plan_restricted",
      "message": "Active subscription needed."
    }
  ]
}

I couldn't test reply-to-conversation action because seems like in order to have a conversation you need select a plan for the account.

I couldn't test new-ticket source because when I make a request to list all tickets I get the following error:

{
    "type": "error.list",
    "request_id": "0047dqf789bmrssl5lkg",
    "errors": [
      {
        "code": "token_unauthorized",
        "message": "Not authorized to access resource"
      }
    ]
  }

So I'm moving this one as blocked in the meantime!

Those are real blockers right there.

I'm happy to drive conversations here:

@vunguyenhung one favor man: for the Pipedream's OAuth 2.0 client for intercom, would you mind try adding the following scopes: "Write Tickets", this is something you could do in Intercom's developer hub.
docs for scopes: https://developers.intercom.com/docs/build-an-integration/learn-more/authentication/oauth-scopes
and kindly let us know once you've done that

@jcortes after Leo adds the appropiate scopes, please try again the "new-ticket" source and let us know the result. for now i'm reaching out to Intercom for access to those endpoints.