[Components] intercom

[pipedream-component-development]

intercom

URLs

• https://developers.intercom.com/docs/references/introduction
• https://developers.intercom.com/docs/references/changelog
• https://developers.intercom.com/docs/references/rest-api/api.intercom.io

Polling Sources

new-ticket

Prompt

Emit new event when a new Ticket is created in Intercom. Props include required configuration for ticket sources and optional filters to track specific priorities or tags.

URLs

• https://developers.intercom.com/docs/references/rest-api/api.intercom.io/tickets/searchtickets

Actions

send-message-to-contact

Prompt

Send a custom message to a contact in Intercom. Props required: 'contact_id' or 'email' to identify the contact, and 'message_body' for the content. Optional props: 'subject' to provide a subject line.

URLs

• https://developers.intercom.com/docs/references/rest-api/api.intercom.io/messages/createmessage

reply-to-conversation

Prompt

Add a reply or a note to an existing conversation thread. Props required: 'conversation_id' to identify the conversation, and 'reply_content' for the reply or note content.

URLs

• https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations/replyconversation

add-tag-to-contact

Prompt

Add a specific tag to a contact. Props required: 'contact_id' or 'email' to identify the contact, and 'tag_name' for the tag to be applied.

URLs

• https://developers.intercom.com/docs/references/rest-api/api.intercom.io/contacts/attachtagtocontact

[jcortes]

@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!

[sergio-eliot-rodriguez]

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.

[sergio-eliot-rodriguez]

Hi Jorge, would you mind retrying your components? App partner representative from Intercom mentioned that account subscription wasn't started when you experienced the errors. "I took a look and I can see that the request you made yesterday was at Jan 13, 2025 @ 22:21:39, but your subscription did not start until Jan 14, 2025 @ 17:23:26. I recommend trying to use the REST API again." Can you test the components again and see if they work now?

…

On Mon, Jan 13, 2025 at 4:08 PM Jorge Cortes ***@***.***> wrote: @sergio-eliot-rodriguez <https://github.com/sergio-eliot-rodriguez> I couldn't test the send-message-to-contact action because I got the following error { ... Message ID: ***@***.***>