Content summarizer via Webhook (ApyHub)
This n8n template empowers you to instantly summarize long pieces of text by sending a simple webhook request. By integrating with ApyHub's summarization API, you can distil complex articles, reports, or messages into concise summaries, significantly boosting efficiency across various domains.
๐ง How it works
- Receive Content Webhook: This node acts as the entry point, listening for incoming POST
requests. It expects a JSON body containing:
- content: The long text you want to summarize.
- summary_length (optional): The desired length of the summary (e.g., 'short', 'medium', 'long'). Defaults to 'medium'. And a header containing your apy-token for the ApyHub API.
- Start Summarization Job: This node sends a POST request to ApyHub's summarization endpoint (api.apyhub.com/sharpapi/api/v1/content/summarize). It passes the content and summary_length from the webhook body, along with your apy-token from the headers. ApyHub processes the text asynchronously, and this node immediately returns a job_id.
- Get Summarization Result: Since ApyHub's summarization is an asynchronous process, this node is crucial. It polls ApyHub's job status endpoint (api.apyhub.com/sharpapi/api/v1/content/summarize/job/status/{{job_id}}) using the job_id obtained from the previous step. It continues to check the status until the summarization is finished, at which point it retrieves the final summarized text.
- Respond with Summarized Content: This node sends the final, distilled summarized text back to the service that initiated the webhook.
๐ค Who is it for?
This workflow is extremely useful for:
- Content Creators & Marketers: Quickly summarize articles for social media snippets, email newsletters, or blog post intros.
- Researchers & Students: Efficiently get the gist of academic papers, reports, or long documents without reading every word.
- Customer Support & Sales Teams: Summarize customer inquiries, long email chains, or call transcripts to quickly understand key issues or discussion points.
- News Aggregators & Media Monitoring: Automatically generate summaries of news articles from various sources for quick consumption.
- Business Professionals: Condense lengthy reports, meeting minutes, or project updates into digestible summaries for busy stakeholders.
- Legal & Compliance: Summarize legal documents or regulatory texts to highlight critical clauses or changes.
- Anyone Dealing with Information Overload: Use it to save time and extract key information from overwhelming amounts of text.
๐Data Structure
When you trigger the webhook, send a **POST ** request with a JSON body and an apy-token in the headers:
{
"content": "Your very long text goes here. This could be an article, a report, a transcript, or any other textual content you want to summarize. The longer the text, the more valuable summarization becomes!",
"summary_length": "medium" // Optional: "short", "medium", or "long"
}
Headers:
apy-token: YOUR_APYHUB_API_KEY
Note: You'll need to obtain an API Key from ApyHub to use their API services. They typically offer a free tier for testing.
The workflow will return a JSON response similar to this (the summary content will vary based on input):
{
"summary": "Max Verstappen believes the Las Vegas Grand Prix is '99% show and 1% sporting event', not looking forward to the razzmatazz. Other drivers, like Fernando Alonso, were more equivocal about the hype, acknowledging the investment and spectacle. Lewis Hamilton praised the city's energy but emphasized it's 'a business, ultimately', believing there will still be good racing.",
"status": "finished",
"result_file_id": "..." // ApyHub might provide a file ID for larger results
}
โ๏ธ Setup Instructions
- Get an ApyHub API Key:
- Go to https://apyhub.com/ and sign up to get your API key.
- Import Workflow: In your n8n editor, click "Import from JSON" and paste the provided workflow JSON.
- Configure Webhook Path:
- Double-click the Receive Content Webhook node.
- In the 'Path' field, set a unique and descriptive path (e.g., /summarize-content).
- Activate Workflow: Save and activate the workflow.
๐ Tips
This content summarizer is a powerful component. Here's how to supercharge it and make it an indispensable part of your automation arsenal:
- Integrate with Document/File Storage:
- Google Drive/Dropbox/OneDrive: Automatically summarize documents uploaded to these services. Add a Watch New Files trigger (if available for your service) or a Cron node to regularly check for new files. Then, read the file content, pass it to this summarizer, and save the summary back to a designated folder or as a comment on the original file.
- CRM/CMS Systems: Pull long notes, customer interactions, or article drafts from your CRM/CMS, summarize them, and update the records with the concise version.
- Email Processing & Triage:
- Email Trigger: Use an Email node to trigger the workflow when new emails arrive. Extract the email body, summarize it, and then:
- Send a shortened summary as a notification to your Slack or Telegram.
- Add a summary to a task management tool (e.g., Trello, Asana) for quicker triaging.
- Create a summary for an email digest.
- Email Trigger: Use an Email node to trigger the workflow when new emails arrive. Extract the email body, summarize it, and then:
- Slack/Discord Bot Integration:
- Create a Slack/Discord command (using a custom webhook or a dedicated Slack/Discord node) where users can paste long text. The bot then sends the summarized version back to the channel.
- Dynamic Summary Length & Options:
- Allow the user to specify summary_length (short, medium, long) in the webhook body, as already implemented.
- Explore ApyHub's documentation for more parameters (if any) and dynamically pass them.
- Error Handling & User Feedback:
- Add an IF node after Get Summarization Result to check for status: 'failed' or error messages. If an error occurs, send a helpful message back to the webhook caller or an internal alert.
- For very long texts that might exceed API limits, add a Function node to truncate the input content if it's too long, and notify the user.
- Multi-language Support (if ApyHub offers it):
- If ApyHub supports summarization in multiple languages, extend the webhook to accept a language parameter and pass it to the API.
- Web Scraping & Article Summaries:
- Combine this with a HTTP Request node to scrape content from a web page (e.g., a news article). Then, pass the extracted article text to this summarizer to get quick insights.
- Data Storage & Archiving:
- Store the original content alongside its summary in a database (e.g., PostgreSQL, MongoDB) or a simple spreadsheet (Google Sheets, Airtable). This creates a searchable, summarized archive of your content.
- Automated Report Generation:
- If you receive daily/weekly reports, use this workflow to summarize key sections, then compile these summaries into a concise digest or dashboard using a Merge node and send it out automatically.
n8n Content Summarizer via Webhook (ApyHub - Placeholder)
This n8n workflow demonstrates a basic webhook listener and responder, serving as a template for more complex integrations. While the directory name suggests "ApyHub" and "content summarization," the provided JSON only includes a webhook trigger, an HTTP Request node (unconfigured), and a webhook response. This workflow is a starting point, ready for customization to interact with external APIs like ApyHub for content summarization.
What it does
This workflow performs the following steps:
- Listens for a Webhook: It starts by waiting for an incoming HTTP request to its unique webhook URL.
- Makes an HTTP Request: It includes an unconfigured HTTP Request node, which is a placeholder for making calls to external APIs (e.g., ApyHub's summarization API).
- Responds to the Webhook: It sends a response back to the caller of the webhook, indicating the workflow's completion or providing initial data.
Prerequisites/Requirements
- An n8n instance (self-hosted or cloud).
- (Optional, for full functionality) An API key or account for a content summarization service like ApyHub or another similar service, if you intend to extend the HTTP Request node.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three dots
...in the top right corner and select "Import from JSON". - Paste the JSON code and click "Import".
- Configure the Webhook:
- The "Webhook" node (ID: 47) will automatically generate a unique URL when the workflow is activated. This is the URL you will send your HTTP requests to.
- You can test this by sending a simple POST request to the webhook URL using a tool like Postman, Insomnia, or
curl.
- Configure the HTTP Request (Optional - for summarization):
- The "HTTP Request" node (ID: 19) is currently unconfigured. To add content summarization functionality:
- Edit the "HTTP Request" node.
- Set the "Method" (e.g., POST).
- Enter the "URL" of your chosen summarization API (e.g., an ApyHub endpoint).
- Configure "Headers" (e.g.,
Content-Type: application/json,Authorization: Bearer YOUR_API_KEY). - Set the "Body Parameters" to send the content you want to summarize, typically by referencing data from the incoming webhook using expressions like
{{ $json.body.textToSummarize }}. - Refer to your chosen summarization API's documentation for specific request details.
- The "HTTP Request" node (ID: 19) is currently unconfigured. To add content summarization functionality:
- Configure the Webhook Response:
- The "Respond to Webhook" node (ID: 535) is configured to send a basic response. You can modify this to return the summarized content from the HTTP Request node using an expression like
{{ $node["HTTP Request"].json.summary }}.
- The "Respond to Webhook" node (ID: 535) is configured to send a basic response. You can modify this to return the summarized content from the HTTP Request node using an expression like
- Activate the Workflow:
- Click the "Activate" toggle in the top right corner of the n8n editor to make the workflow live and ready to receive webhook calls.
Once activated, any HTTP request sent to the Webhook URL will trigger this workflow. If you configure the HTTP Request node, it will process the incoming data, call the external API, and then respond to the original webhook caller.
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.
Generate 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
Automate 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.