Import

Purpose

The import module brings external data into outsend as a pipeline source. It is pipeline-internal — see /docs/concepts/pipeline-orchestration — and produces a normalized POI list that downstream enrichment, verification, or processing nodes can consume. Unlike scrap, import consumes no extraction quota (EF cost is zero).

Inputs

The node config exposes a single discriminator, source, with three mutually exclusive modes.

paste — inline CSV

The text payload is parsed as CSV by the shared resolution layer (app/column_map.py). The delimiter is auto-detected (comma, semicolon, or tab); UTF-8 is expected, with UTF-8 BOM and Latin-1 / cp1252 accepted as fallbacks. Headers are not mandatory: column names are matched flexibly against accepted aliases (a Website, url, e-mail or raison sociale header maps to the right canonical column), and a header-less sheet is auto-detected — its columns are then inferred from their content. Either way the import emits a notice (info banner on the job page, ⓘ on the dashboard) reporting what was auto-mapped, inferred, or ignored, so the mapping is never silent.

url — public spreadsheet

The url payload points to a publicly readable spreadsheet (typical shape: https://docs.google.com/spreadsheets/d/.../edit#gid=0). The sheet must be shared as "anyone with the link can view" — outsend does not authenticate to third-party providers. The fetched content is parsed with the same CSV rules as paste.

from_job — recent scrap reuse

The from_job_id payload references a previous scrap job. The reference is validated server-side at job creation:

When valid, the resulting import inherits all columns produced by the source scrap.

Outputs

import produces a normalized POI list, declared in the pipeline registry as output: "pois" — the same shape scrap emits. Downstream nodes that accept pois_any (reviews, emails, socials, dead-check, techstack, ads-intelligence, brand-assets) chain directly. Nodes that require pois_email (verify) chain only if the imported CSV already carries an email column.

The column set is dynamic: it mirrors whatever the source provides. The registry declares needs: [] and produces: [] for this reason — the module is permissive on input and propagates the input schema as output.

Lifecycle

Standard job lifecycle — see /docs/concepts/jobs-lifecycle. The job is linked to its pipeline via pipeline_id and pipeline_node_id and runs as soon as the pipeline transitions to running.

Pipeline

import is a root node. It accepts no upstream edges. Any node whose input is pois_any, any_pois, or pois_email (when the CSV carries emails) can be wired downstream.

Registry: needs: [], produces: [].

Endpoints

The import module is not exposed as a standalone job endpoint — it is pipeline-internal (see /docs/concepts/pipeline-orchestration) and created only as a pipeline root. Two adjacent endpoints are useful when assembling an import:

The pipeline node payload itself follows this shape:

{
  "type": "import",
  "config": {
    "source": "paste",
    "text": "nom,site_web\n...",
    "url": "",
    "from_job_id": ""
  }
}

Exactly one of text, url, from_job_id is read, determined by source. The unused fields are persisted as empty strings.

Limits

Global limits — see /docs/concepts/limits. Module-specific:

Errors

What's next