An n8n developer building a workflow that reads Slack messages needs structured content from each message before the workflow can act on it. Accessing Slack programmatically requires OAuth credentials with channel-specific scopes and cursor-based pagination through the conversations history API, which adds setup that belongs outside the workflow itself. EnConvert Distill accepts the URL of a Slack page that opens without signing in, applies a schema the developer defines, and returns structured fields in one synchronous HTTP call. The workflow gets schema-defined message content with no Slack API token and no pagination step.
How to Summarise Slack with n8n
Summarise Slack messages inside an n8n workflow with EnConvert Distill, which returns schema-defined fields for up to 50 URLs in one synchronous call
Get API keyExample
javascript
// Code node: set to "Run Once for All Items"
const API_KEY = $env.ENCONVERT_API_KEY; // set ENCONVERT_API_KEY in the n8n environment (needs N8N_BLOCK_ENV_ACCESS_IN_NODE=false)
// The fields each result returns. The response keys match these names exactly.
// Each description tells the extractor to leave a field empty rather than guess.
const SCHEMA = {
message_content:
"The text of the message or messages on the page. Return an empty string if no message text is visible.",
channel_name: "The channel name shown on the page. Return an empty string if none is shown.",
sender:
"The display name of the person who posted the message. Return an empty string if none is shown.",
timestamp:
"The date and time of the message, exactly as the page shows it. Return an empty string if none is shown.",
};
const urls = $input.all().map((item) => item.json.url).filter(Boolean);
if (urls.length > 50) {
throw new Error("Distill accepts at most 50 URLs per call. Split the list with a Loop Over Items node.");
}
// One synchronous call: no job_id, no polling, no download step
const response = await this.helpers.httpRequest({
method: "POST",
url: "https://api.enconvert.com/v2/distill",
headers: {
"X-API-Key": API_KEY,
"Content-Type": "application/json",
},
body: { urls, schema: SCHEMA },
json: true,
returnFullResponse: true,
ignoreHttpStatusErrors: true,
timeout: 300000,
});
// Distill runs on paid plans only, and the free tier returns 402
if (response.statusCode === 402) {
throw new Error("Distill requires a paid plan.");
}
if (response.statusCode >= 400) {
throw new Error(`Distill request failed with status ${response.statusCode}.`);
}
// Return one item per URL so a downstream IF node can filter on the skipped field
return response.body.results.map((result) => {
if (result.status !== "completed") {
return { json: { url: result.url, skipped: true, reason: `status ${result.status}` } };
}
// A render_quality below 0.5 may mean a login wall or challenge page
const renderQuality = result.render_quality ?? 1.0;
if (renderQuality < 0.5) {
return {
json: {
url: result.url,
skipped: true,
reason: `low render quality (${renderQuality}), likely a login page`,
},
};
}
const data = result.data; // keys match SCHEMA exactly
if (!data.message_content) {
return { json: { url: result.url, skipped: true, reason: "no message content found" } };
}
return { json: { url: result.url, skipped: false, ...data } };
});
What you get back
Distill returns schema-defined fields inline as structured JSON in the data object, with no polling and no job_id. The render_quality score lets the workflow flag a page before acting on incomplete content, and the skipped field on each output item routes failed or low-quality results away from downstream nodes. Reading Slack messages natively requires OAuth credentials with channel scopes and cursor-based pagination through the conversations history API, while Distill returns schema-defined fields from the message URL in one call.