Automated Bug Reporting from Marker.io to Intercom - n8n Workflow

• Customer Support Teams who use Intercom to manage all customer communications.


• Product Managers needing a single source of truth for incoming bugs.


• Software Development teams aiming to receive detailed, contextual bug reports immediately.


• Users looking for advanced, pre-built n8n templates for integration between SaaS tools.

This powerful automation solves the critical disconnect between bug reporting tools and customer communication platforms. While Marker.io excels at capturing visual bugs with rich technical metadata (browser details, console logs, environment context), support teams often live within Intercom. This n8n workflow bridges that gap. Upon receiving a new Marker.io issue, the n8n node sequence automatically creates or updates the reporter's contact profile in Intercom, starts a new conversation (providing the user-facing details), and crucially, adds a comprehensive internal note containing all the technical specifications, context strings, and direct Marker.io links. This ensures your support team has zero manual entry and all the necessary context to triage and resolve issues immediately. By implementing this n8n template, organizations ensure efficient communication and rapid issue resolution. Using this n8n workflow saves time and improves developer context.

The process begins with the Webhook n8n trigger node, which is configured to listen for new issues reported via Marker.io. When a new bug report is submitted, Marker.io sends a payload to the webhook URL.

1. Data Parsing: The Format Marker.io Data custom code n8n node meticulously extracts technical fields like browser version, operating system, issue type, priority, and links from the incoming data. It prepares two distinct bodies: a simple conversation starter for the user (messageBody) and a detailed technical note for internal staff (nodeBody).


2. Contact Management: The next n8n node, an HTTP Request, attempts to Create/Update Contact in Intercom using the reporter's email and name extracted in the previous step.


3. Conversation Initiation: Following contact preparation, another HTTP Request n8n node named Create Conversation opens a new support ticket in Intercom, displaying the public-facing title and description parsed earlier.


4. Context Addition: Finally, the Add Internal Note n8n node fires. It takes the ID of the newly created conversation and posts the detailed technical note into the ticket as an internal comment. This note provides essential context (OS, Browser, Context String, Marker.io public link) directly within the Intercom interface, completing the automated flow of this powerful n8n workflow.

To use this specialized n8n template, follow these setup steps:

1. Import the n8n Workflow: Copy the provided JSON data and import it directly into your n8n instance via the Workflows section.


2. Configure the n8n Trigger: Select the Webhook n8n node. Save the workflow to generate the production URL. Copy this unique URL.


3. Set up Marker.io Webhook: Navigate to your Marker.io Workspace Settings and Webhooks. Create a new webhook, paste the URL copied from your n8n trigger, and ensure you select "Issue Created" as the event trigger.


4. Intercom Credentials: This n8n workflow uses three HTTP Request n8n nodes connecting to Intercom. You must establish or select your Intercom API credentials (using a token with contact and conversation write permissions) for all three nodes.


5. Set Admin ID: In the Add Internal Note n8n node parameters, you must provide the admin_id of an administrator in your Intercom workspace. This ID is used to attribute the internal note correctly.


6. Testing: Initiate a test bug report through your Marker.io widget. Activate the n8n workflow manually or wait for the report to trigger the sequence, verifying that the conversation and the detailed internal note appear correctly in Intercom.

This n8n workflow relies on core nodes and Intercom API integrations:

Webhook (n8n trigger): Acts as the starting point, receiving POST data from Marker.io upon issue creation. It uses a unique path for secure communication. This is the starting n8n trigger.
Format Marker.io Data (Code n8n node): Essential for transforming raw Marker.io JSON into usable variables. Function: It extracts critical fields like reporter details, browser, and OS, and generates the highly structured internal note body (nodeBody) containing technical specifications, links, and custom data fields.
Create/Update Contact (HTTP Request n8n node): Connects to the Intercom /contacts endpoint. Function: Ensures the reporter exists in Intercom before conversation creation, using email and name from the previous n8n node output. Configured to continue on fail.
Create Conversation (HTTP Request n8n node): Connects to the Intercom /conversations endpoint. Function: Initiates the support conversation using the reporter's email and the simple messageBody generated by the Code n8n node.

• Add Internal Note (HTTP Request n8n node): Connects to the Intercom /conversations/{id}/parts endpoint. Function: Appends the comprehensive technical details (including browser, OS, URL, Marker.io link) as a private note, maximizing context for the support agent. It relies on the conversation ID outputted by the preceding n8n node.