Skip to main content

Automate Marker.io issues to Intercom conversations with full technical context

Workflow preview

Workflow preview
100%
Automate Marker.io issues to Intercom conversations with full technical context preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Automatically create Intercom conversations with full technical context when your team receive new Marker.io issues What this template does This workflow creates a seamless bridge between Marker...

Best for

  • Ticket Management automation workflows
  • Multimodal AI automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.webhook, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Marker.io.

Original n8n.io source

1.1 Workflow description

Title
Automate Marker.io issues to Intercom conversations with full technical context
Workflow name
Automate Marker.io issues to Intercom conversations with full technical context

Automatically create Intercom conversations with full technical context when your team receive new Marker.io issues

🎯 What this template does

This workflow creates a seamless bridge between Marker.io and Intercom, your customer support platform. Every issue submitted through Marker.io's widget automatically becomes a trackable conversation in Intercom, complete with technical details and visual context. Centralizing customers issues in Intercom helps your support agents continue the conversation right where they work every day.

When a bug is reported, the workflow:

  • Creates or updates the reporter as an Intercom contact
  • Opens a new conversation with the reporter and the all issue details
  • Adds a comprehensive internal note with technical metadata
  • Preserves all screenshots, browser info, and custom data

✨ Benefits

  • Zero manual entry - All bug details transfer automatically
  • Instant visibility - Support agents sees issues immediately
  • Rich context - Technical details preserved for developers
  • Better collaboration - Single source of truth for bugs
  • Faster resolution - No time wasted gathering information

πŸ’‘ Use Cases

  • Product Teams: Streamline bug triage without switching tools
  • Support Teams: Get technical context for customer-reported issues
  • Development Teams: Access browser info, console logs and network logs directly from the support tickets

πŸ”§ How it works

  1. n8n Webhook receives Marker.io bug report data
  2. Format and extract relevant information from the payload
  3. Create/update contact in Intercom with reporter details
  4. Start conversation with the Title and Bug description
  5. Add internal note with full technical context and Marker.io links for the support agent

The result is a perfectly organized support ticket that your team can act on immediately, with all the context they need to reproduce and resolve the issue.

πŸ“‹ Prerequisites

  • Marker.io account with webhook capabilities
  • Intercom account with API access
  • Intercom Access Token with appropriate permissions
  • Admin ID from your Intercom workspace

πŸš€ Setup Instructions

  1. Import this workflow into your n8n instance

  2. Configure the Webhook:

    • Copy the test/production webhook URL after saving
    • Add to Marker.io: Workspace Settings β†’ Webhooks β†’ Create webhook
    • Select "Issue Created" as the trigger event
  3. Set up Intercom credentials:

    • Create an Intercom app or use existing API credentials from the Intercom Develper Hub
    • Add credentials to both HTTP Request nodes
    • Update the admin_id in the "Add Internal Note" node with the id of one of your intercom admin
  4. Test the integration:

    • Create a test issue in Marker.io
    • Verify the conversation appears in Intercom
    • Check that all data transfers correctly

πŸ“Š Data Captured

Customer-facing message includes:

  • Issue title
  • Description

Internal note includes:

  • πŸ†” Marker ID
  • πŸ“Š Priority level and issue type
  • πŸ“… Due date (if set)
  • πŸ–₯️ Browser and OS details
  • πŸ€“ Develper Console & Network logs
  • 🌐 Website URL where issue occurred
  • πŸ”— Direct link to Marker.io issue
  • πŸ“·Β Screenshot of the issue
  • πŸ“¦ Any custom data fields

β†’ Read more about our webhook events

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Webhook1

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2

Block 2 - Format Marker.io Data1

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 3 - Create/Update Contact1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 4 - Create Conversation1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 5 - Add Internal Note1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 6 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Automate Marker.io issues to Intercom conversations with full technical context
Complexity intermediate
Nodes 7
Categories Ticket Management, Multimodal AI
Author Marker.io
Published 14 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7388/7388.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automate Marker.io issues to Intercom conversations with full technical context do?

Automatically create Intercom conversations with full technical context when your team receive new Marker.io issues What this template does This workflow creates a seamless bridge between Marker...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management, Multimodal AI use case.