Automate Marker.io issues to ServiceNow incidents with full technical context
Marker.io to ServiceNow Integration
Automatically create ServiceNow incidents with full technical context when bugs are reported through Marker.io
🎯 What this template does
This workflow creates a seamless bridge between Marker.io and ServiceNow, your IT service management platform. Every issue submitted through Marker.io's widget automatically becomes a trackable incident in ServiceNow, complete with technical details and visual context. This ensures your IT team can track, prioritize, and resolve bugs efficiently within their existing ITSM workflow.
When a bug is reported, the workflow:
- Captures the complete Marker.io webhook payload
- Formats all technical details and metadata
- Creates a new incident in ServiceNow with the reporter information
- Includes comprehensive technical context and Marker.io links
- Preserves screenshots, browser info, and custom data
✨ Benefits
- Automated ticket creation - No manual data entry required
- Complete context - All bug details transfer automatically
- Faster triage - IT teams see issues immediately in ServiceNow
- Better tracking - Leverage ServiceNow's incident management capabilities
- Rich debugging info - Browser, OS, and screenshot details preserved
💡 Use Cases
- IT Service Desks: Streamline bug reporting from end users
- Development Teams: Track production issues with full technical context
- QA Teams: Convert test findings directly into trackable incidents
- Support Teams: Escalate customer-reported bugs to IT with complete details
🔧 How it works
- N8N Webhook receives Marker.io bug report data
- JavaScript node formats and extracts relevant information
- ServiceNow node creates incident with formatted details
- Incident includes title, description, reporter info, and technical metadata
- Links preserved to both public and private Marker.io views
The result is a fully documented ServiceNow incident that your IT team can immediately action, with all the context needed to reproduce and resolve the issue.
📋 Prerequisites
- Marker.io account with webhook capabilities
- ServiceNow instance with API access enabled
- ServiceNow credentials (username/password or OAuth)
- Appropriate ServiceNow permissions to create incidents
🚀 Setup Instructions
- Import this workflow into your n8n instance
- Configure the Webhook:
- Copy the production webhook URL after saving
- Add to Marker.io: Workspace Settings → Webhooks → Create webhook
- Select "Issue Created" as the trigger event
- Set up ServiceNow credentials:
- In n8n, create new ServiceNow credentials
- Enter your ServiceNow instance URL
- Add username and password for a service account
- Test the connection
- Customize field mappings (optional):
- Modify the JavaScript code to map additional fields
- Adjust priority mappings to match your ServiceNow setup
- Add custom field mappings as needed
- Test the integration:
- Create a test issue in Marker.io
- Verify the incident appears in ServiceNow
- Check that all data transfers correctly
📊 Data Captured
ServiceNow Incident includes:
- Short Description: Issue title from Marker.io
- Description containing:
- 🐛 Issue title and ID
- 📊 Priority level and issue type
- 📅 Due date (if set)
- 📝 Full issue description
- 🖥️ Browser version and details
- 💻 Operating system information
- 🌐 Website URL where issue occurred
- 🔗 Direct links to Marker.io issue (public and private)
- 📦 Any custom data fields
- 📷 Screenshot URL with proper formatting
🔄 Workflow Components
- Webhook Node: Receives Marker.io POST requests
- Code Node: Processes and formats the data using JavaScript
- ServiceNow Node: Creates the incident using ServiceNow API
→ Read more about Marker.io webhook events
🚨 Troubleshooting
Webhook not triggering:
- Verify webhook URL is correctly copied from n8n to Marker.io
- Check that "Issue Created" event is selected in Marker.io webhook settings
- Ensure webhook is set to "Active" status in Marker.io
- Test with Marker.io's webhook tester feature
- Check n8n workflow is active and not in testing mode
ServiceNow incident not created:
- Verify ServiceNow credentials are correct and have not expired
- Check that the service account has permissions to create incidents
- Ensure ServiceNow instance URL is correct (include https://)
- Test ServiceNow connection directly in n8n credentials settings
- Check ServiceNow API rate limits haven't been exceeded
Missing or incorrect data:
- Screenshot URL broken: The workflow already handles URL formatting, but verify Marker.io is generating screenshots
- Custom data missing: Ensure custom fields exist in Marker.io before sending
- Due date formatting issues: Check your ServiceNow date format requirements
JavaScript errors in Format node:
- Check webhook payload structure hasn't changed in Marker.io updates
- Verify all field paths match current Marker.io webhook schema
- Use n8n's data pinning to debug with actual webhook data
- Check for undefined values when optional fields are missing
Connection issues:
- ServiceNow timeout: Increase timeout in node settings if needed
- SSL/Certificate errors: Check ServiceNow instance SSL configuration
- Network restrictions: Ensure n8n can reach your ServiceNow instance
- Authentication failures: Regenerate ServiceNow credentials if needed
Testing tips:
- Use n8n's "Execute Workflow" with pinned test data
- Enable webhook test mode in Marker.io for safe testing
- Check ServiceNow incident logs for detailed error messages
- Monitor n8n execution logs for specific failure points
Automate Marker.io Issues to ServiceNow Incidents
This n8n workflow automates the creation of ServiceNow incidents from incoming Marker.io issues. It acts as a bridge, transforming the data received from Marker.io into a format suitable for ServiceNow, ensuring that reported issues are promptly converted into actionable incidents.
What it does
This workflow simplifies the process of escalating user-reported issues (e.g., bugs, feedback) captured via Marker.io directly into your ServiceNow instance.
- Listens for Marker.io Webhooks: The workflow is triggered by an incoming webhook, expecting data from Marker.io when a new issue is reported.
- Transforms Data for ServiceNow: A Code node processes the incoming Marker.io data, extracting relevant information and formatting it to match the expected structure for a ServiceNow incident. This includes mapping fields like issue description, reporter information, and any attached context.
- Creates ServiceNow Incident: The transformed data is then used to create a new incident in ServiceNow, ensuring that all necessary details from the Marker.io report are captured.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Marker.io Account: An active Marker.io account configured to send webhooks.
- ServiceNow Account: Access to a ServiceNow instance with appropriate permissions to create incidents.
- ServiceNow n8n Credential: A configured ServiceNow credential in n8n (OAuth2 or Basic Auth).
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Webhook:
- Activate the "Webhook" node.
- Copy the "Webhook URL" provided by the node.
- In your Marker.io project settings, configure a webhook to send issue data to this URL.
- Configure ServiceNow Credential:
- Open the "ServiceNow" node.
- Select or create your ServiceNow credential. If creating a new one, provide your ServiceNow instance URL and authentication details (e.g., username/password for Basic Auth, or OAuth2 client ID/secret).
- Review and Customize Code Node (Optional but Recommended):
- The "Code" node currently has no custom logic defined in the provided JSON. You must add JavaScript code here to transform the incoming Marker.io webhook data into the desired format for your ServiceNow incident.
- Example data to map might include:
short_description: From Marker.io issue title.description: From Marker.io issue description, potentially including URL, browser info, etc.caller_id: If you can map the Marker.io reporter to a ServiceNow user.category,subcategory,impact,urgency: Based on your Marker.io forms or default values.work_notes: To include links back to the Marker.io report or attachments.
- The output of this Code node should be an object (or an array of objects) that directly corresponds to the fields you want to set when creating a ServiceNow incident.
- Activate the Workflow: Once all configurations are complete, activate the workflow.
Now, whenever a new issue is reported in Marker.io, it will trigger this workflow, transform the data, and create a corresponding incident in ServiceNow.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
By Ranjan DailataGenerate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
By Daniel NkenchoAutomate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.
By Le Nguyen