Marker.io에서 Intercom으로의 버그 리포트 자동화 (전체 기술 컨텍스트 포함)
중급
이것은Ticket Management, Multimodal AI분야의자동화 워크플로우로, 7개의 노드를 포함합니다.주로 Code, Webhook, HttpRequest 등의 노드를 사용하며. Marker.io에서 Intercom으로의 버그 리포트 자동화 (전체 기술 컨텍스트 포함)
사전 요구사항
- •HTTP Webhook 엔드포인트(n8n이 자동으로 생성)
- •대상 API의 인증 정보가 필요할 수 있음
사용된 노드 (7)
워크플로우 미리보기
노드 연결 관계를 시각적으로 표시하며, 확대/축소 및 이동을 지원합니다
워크플로우 내보내기
다음 JSON 구성을 복사하여 n8n에 가져오면 이 워크플로우를 사용할 수 있습니다
{
"meta": {
"instanceId": "b8d4a47d3554c1f7fcd3ee16a413d67d707f3769dee6d5380a7d25c6b616c836"
},
"nodes": [
{
"id": "1422c63e-e65c-4db9-a1a5-ea6badc8299c",
"name": "Webhook",
"type": "n8n-nodes-base.webhook",
"position": [
0,
0
],
"webhookId": "e373c60f-8530-4368-a486-fcc41f410b6c",
"parameters": {
"path": "e373c60f-8530-4368-a486-fcc41f410b6c",
"options": {},
"httpMethod": "POST"
},
"typeVersion": 2
},
{
"id": "344e0ae2-f317-4db0-9156-2eb9be1ff117",
"name": "Marker.io 데이터 형식 지정",
"type": "n8n-nodes-base.code",
"position": [
220,
0
],
"parameters": {
"jsCode": "// Extract data from Marker.io webhook\nconst data = $input.first().json.body.data;\n\n// Format the conversation message\nconst issueTitle = data.title;\nconst issueDescription = data.description;\nconst markerId = data.markerId;\nconst priority = data.priority;\nconst issueType = data.issueType.name;\nconst publicUrl = data.publicUrl;\nconst privateUrl = data.privateUrl;\nconst dueDate = data.dueDate;\nconst browser = `${data.browser.name} ${data.browser.version}`;\nconst os = `${data.operatingSystem.family} ${data.operatingSystem.version}`;\nconst website = data.website.url;\nconst contextString = data.contextString;\n\n// Create formatted message body with Marker.io ticket link\nconst messageBody = `${issueTitle}\n${issueDescription}`;\n\n// Create formatted message body with Marker.io ticket link\nconst noteBody = `🐛 **New Issue Reported via Marker.io**\n\n**Issue:** ${issueTitle}\n**ID:** ${markerId}\n**Type:** ${issueType}\n**Priority:** ${priority}\n**Due Date:** ${dueDate ? new Date(dueDate).toLocaleDateString() : 'Not set'}\n\n**Description:**\n${issueDescription}\n\n**Technical Details:**\n• Browser: ${browser}\n• OS: ${os}\n• Website: ${website}\n• Context: ${contextString}\n\n**Marker.io Links:**\n• 🔗 [View Issue](${publicUrl})\n\n**Custom Data:**\n${Object.entries(data.customData || {}).map(([key, value]) => `• ${key}: ${value}`).join('\\n')}`;\n\nreturn [{\n json: {\n reporterEmail: data.reporter.email,\n reporterName: data.reporter.name,\n messageBody: messageBody,\n nodeBody: noteBody,\n issueId: data.id,\n markerId: markerId,\n priority: priority,\n issueType: issueType,\n publicUrl: publicUrl,\n privateUrl: privateUrl,\n projectId: data.project.id\n }\n}];"
},
"typeVersion": 2
},
{
"id": "c6e59c93-8830-403a-adee-b80f4434359d",
"name": "연락처 생성/업데이트",
"type": "n8n-nodes-base.httpRequest",
"position": [
440,
0
],
"parameters": {
"url": "https://api.intercom.io/contacts",
"method": "POST",
"options": {},
"sendBody": true,
"authentication": "predefinedCredentialType",
"bodyParameters": {
"parameters": [
{
"name": "role",
"value": "user"
},
{
"name": "email",
"value": "={{ $json.reporterEmail }}"
},
{
"name": "name",
"value": "={{ $json.reporterName }}"
}
]
},
"nodeCredentialType": "intercomApi"
},
"credentials": {
"intercomApi": {
"id": "",
"name": ""
}
},
"typeVersion": 4.2,
"continueOnFail": true
},
{
"id": "ac375334-4e47-47b2-a6dd-ae95ff5a2039",
"name": "대화 생성",
"type": "n8n-nodes-base.httpRequest",
"position": [
660,
0
],
"parameters": {
"url": "https://api.intercom.io/conversations",
"method": "POST",
"options": {},
"sendBody": true,
"authentication": "predefinedCredentialType",
"bodyParameters": {
"parameters": [
{
"name": "from",
"value": "={{ { \"type\": \"user\", \"email\": $('Format Marker.io Data').item.json.reporterEmail } }}"
},
{
"name": "body",
"value": "={{ $('Format Marker.io Data').item.json.messageBody }}"
},
{
"name": "message_type",
"value": "inapp"
}
]
},
"nodeCredentialType": "intercomApi"
},
"credentials": {
"intercomApi": {
"id": "",
"name": ""
}
},
"typeVersion": 4.2
},
{
"id": "ac1a3de3-022a-4aff-b330-6b8c912ecb3b",
"name": "내부 메모 추가",
"type": "n8n-nodes-base.httpRequest",
"position": [
880,
0
],
"parameters": {
"url": "=https://api.intercom.io/conversations/{{ $json.conversation_id }}/parts",
"method": "POST",
"options": {},
"sendBody": true,
"jsonHeaders": "[\n {\n \"name\": \"Accept\",\n \"value\": \"application/json\"\n },\n {\n \"name\": \"Intercom-Version\",\n \"value\": \"2.13\"\n }\n ]",
"sendHeaders": true,
"authentication": "predefinedCredentialType",
"bodyParameters": {
"parameters": [
{
"name": "message_type",
"value": "note"
},
{
"name": "body",
"value": "={{ $('Format Marker.io Data').item.json.nodeBody }}"
},
{
"name": "admin_id",
"value": ""
}
]
},
"specifyHeaders": "json",
"nodeCredentialType": "intercomApi"
},
"credentials": {
"intercomApi": {
"id": "",
"name": ""
}
},
"typeVersion": 4.2
},
{
"id": "e66ca32c-c7c6-459a-a276-d4e3199a589b",
"name": "Sticky Note",
"type": "n8n-nodes-base.stickyNote",
"position": [
-820,
-640
],
"parameters": {
"width": 700,
"height": 2220,
"content": "# Marker.io to Intercom integration\n\n**Automatically create Intercom conversations with full technical context when your team receive new Marker.io issues**\n\n## 🎯 What this template does\n\nThis 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.\n\nWhen a bug is reported, the workflow:\n- Creates or updates the reporter as an Intercom contact\n- Opens a new conversation with the reporter and the all issue details\n- Adds a comprehensive internal note with technical metadata\n- Preserves all screenshots, browser info, and custom data\n\n## ✨ Benefits\n\n- **Zero manual entry** - All bug details transfer automatically\n- **Instant visibility** - Support agents sees issues immediately \n- **Rich context** - Technical details preserved for developers\n- **Better collaboration** - Single source of truth for bugs\n- **Faster resolution** - No time wasted gathering information\n\n## 💡 Use Cases\n\n- **Product Teams**: Streamline bug triage without switching tools\n- **Support Teams**: Get technical context for customer-reported issues\n- **Development Teams**: Access browser info, console logs and network logs directly from the support tickets\n\n## 🔧 How it works\n\n1. **N8N Webhook receives** Marker.io bug report data\n2. **Format and extract** relevant information from the payload\n3. **Create/update contact** in Intercom with reporter details\n4. **Start conversation** with the Title and Bug description\n5. **Add internal note** with full technical context and Marker.io links for the support agent\n\nThe 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.\n\n## 📋 Prerequisites\n\n- **Marker.io account** with webhook capabilities\n- **Intercom account** with API access\n- **Intercom Access Token** with appropriate permissions\n- **Admin ID** from your Intercom workspace\n\n## 🚀 Setup Instructions\n\n1. **Import this workflow** into your n8n instance\n\n2. **Configure the Webhook**:\n - Copy the test/production webhook URL after saving\n - Add to Marker.io: Workspace Settings → Webhooks → Create webhook\n - Select \"Issue Created\" as the trigger event\n\n3. **Set up Intercom credentials**:\n - Create an Intercom app or use existing API credentials from the Intercom Develper Hub\n - Add credentials to both HTTP Request nodes\n - Update the `admin_id` in the \"Add Internal Note\" node with the id of one of your intercom admin\n\n4. **Test the integration**:\n - Create a test issue in Marker.io\n - Verify the conversation appears in Intercom\n - Check that all data transfers correctly\n\n\n## 📊 Data Captured\n\n### Customer-facing message includes:\n- Issue title\n- Description\n\n### Internal note includes:\n- 🆔 Marker ID\n- 📊 Priority level and issue type\n- 📅 Due date (if set)\n- 🖥️ Browser and OS details\n- 🤓 Develper Console & Network logs\n- 🌐 Website URL where issue occurred\n- 🔗 Direct link to Marker.io issue\n- 📦 Any custom data fields\n\n[→ Read more about our webhook events](https://help.marker.io/en/articles/3738778-webhook-notifications)"
},
"typeVersion": 1
},
{
"id": "8cb11d36-ef6b-498a-9c78-272b592357b4",
"name": "Sticky Note1",
"type": "n8n-nodes-base.stickyNote",
"position": [
-40,
540
],
"parameters": {
"color": 5,
"width": 440,
"height": 420,
"content": "## 🚨 Troubleshooting\n\n**Webhook not triggering:**\n- Verify webhook URL is correct in Marker.io\n- Check that \"Issue Created\" event is selected\n- Test with Marker.io's webhook tester\n\n**Contact creation failing:**\n- Ensure Intercom API token has contact write permissions\n- Check email format in reporter data\n\n**Missing internal note:**\n- Verify admin_id is correct (find in Intercom settings)\n- Ensure API token belongs to the admin user\n\n**Data not appearing:**\n- Check webhook payload structure hasn't changed\n- Verify all field paths in the Format node"
},
"typeVersion": 1
}
],
"pinData": {},
"connections": {
"1422c63e-e65c-4db9-a1a5-ea6badc8299c": {
"main": [
[
{
"node": "344e0ae2-f317-4db0-9156-2eb9be1ff117",
"type": "main",
"index": 0
}
]
]
},
"ac375334-4e47-47b2-a6dd-ae95ff5a2039": {
"main": [
[
{
"node": "ac1a3de3-022a-4aff-b330-6b8c912ecb3b",
"type": "main",
"index": 0
}
]
]
},
"c6e59c93-8830-403a-adee-b80f4434359d": {
"main": [
[
{
"node": "ac375334-4e47-47b2-a6dd-ae95ff5a2039",
"type": "main",
"index": 0
}
]
]
},
"344e0ae2-f317-4db0-9156-2eb9be1ff117": {
"main": [
[
{
"node": "c6e59c93-8830-403a-adee-b80f4434359d",
"type": "main",
"index": 0
}
]
]
}
}
}자주 묻는 질문
이 워크플로우를 어떻게 사용하나요?
위의 JSON 구성 코드를 복사하여 n8n 인스턴스에서 새 워크플로우를 생성하고 "JSON에서 가져오기"를 선택한 후, 구성을 붙여넣고 필요에 따라 인증 설정을 수정하세요.
이 워크플로우는 어떤 시나리오에 적합한가요?
중급 - 티켓 관리, 멀티모달 AI
유료인가요?
이 워크플로우는 완전히 무료이며 직접 가져와 사용할 수 있습니다. 다만, 워크플로우에서 사용하는 타사 서비스(예: OpenAI API)는 사용자 직접 비용을 지불해야 할 수 있습니다.
관련 워크플로우 추천
Marker.io 시각적 오류 보고서를 기술적 상황을 포함한 Zendesk 지원 작업지로 변환
Marker.io 시각적 오류 보고서를 기술적 상황을 포함한 Zendesk 지원 티켓으로 변환
Code
Webhook
Http Request
+
Code
Webhook
Http Request
7 노드Marker.io
티켓 관리
전체 기술 컨텍스트를 사용하여 Marker.io 문제를 ServiceNow 인시던트로 자동 변환
전체 기술 컨텍스트를 사용하여 Marker.io 문제를 ServiceNow 인시던트로 자동 변환
Code
Webhook
Service Now
+
Code
Webhook
Service Now
5 노드Marker.io
티켓 관리
OpenAI 어시스턴트 기반 Gmail 자동 회신 초안 생성
OpenAI 어시스턴트 기반 Gmail 자동 응답 초안 생성
Set
Code
Gmail
+
Set
Code
Gmail
23 노드Hichul
티켓 관리
Claude AI와 자동 업그레이드를 사용하여 공감형 고객 답변 생성
사용하여 Claude AI와 자동 업그레이드를 통해 공감형 고객 답변 생성
If
Set
Code
+
If
Set
Code
21 노드Yusuke
티켓 관리
Telegram AI 가사 학습 봇 — 번역, 요약, 어휘
Telegram AI 가사 학습 봇 — 번역, 요약, 어휘
If
Set
Code
+
If
Set
Code
30 노드Raphael De Carvalho Florencio
콘텐츠 제작
WhatsApp AI 영화 추천기
WhatsApp AI 영화 추천기
If
Set
Code
+
If
Set
Code
20 노드Oneclick AI Squad
지원 챗봇
워크플로우 정보
난이도
중급
노드 수7
카테고리2
노드 유형4
저자
Marker.io
@markerioMarker.io is a visual feedback and bug reporting tool primarily used by web development and design teams. It allows users to capture screenshots, annotate them with comments and drawings, and then send them directly to project management or issue tracking tools like Jira, Trello, GitHub, or Asana.
외부 링크
n8n.io에서 보기 →
이 워크플로우 공유