What ElTract does — and what it does not claim today.

ElTract is a web-data platform for collecting information from public websites, structuring it into working datasets, reviewing and importing data, maintaining company and people context, preserving change history and connecting selected data to monitoring, automation and configured outreach workflows.

ElTract organizes work around projects, runs, results, datasets, imports, company and people records, Data Quality, Web Memory, Monitor, Automate and Engage. Some capabilities, including crawling, scheduled monitoring, workflow execution and message delivery, depend on their dedicated runtime or provider configuration.

Web extraction is one part of ElTract, but the product is broader than a one-off scraper. It keeps projects, run history, structured results, review, imports, company and people context, change history and downstream workflows in the same product.

Yes. Public-web crawling and extraction are implemented. Actual crawl execution requires the ElTract crawl worker, Playwright and Redis to be deployed and healthy.

ElTract provides project configuration and source analysis so normal collection work does not require you to maintain a separate scraping script for each project. Source analysis can compare extraction approaches and detected fields before a crawl starts.

Yes. The current product supports CSV and XLSX import. You can map columns, select workbook sheets, preview create/update/skip/conflict decisions and apply the persisted preview to project data.

Yes, for selected public sources. Monitor creation, supported schedules, manual runs, run history and detected changes are implemented. Scheduled monitoring and change detection require the ElTract crawl worker and Redis.

Web Memory is ElTract’s entity history and change-intelligence layer. It preserves observations and timeline context so an important previous value or source event does not disappear when a newer value is recorded.

Yes. ElTract includes organization-scoped company and people records plus lists, pipeline/opportunities, tasks, notes, activity and source evidence.

ElTract has an implemented Data Quality and enrichment foundation, including reviewable enrichment candidates and provider availability states. Third-party enrichment coverage depends on configured providers and should not be assumed to be universally available.

Yes. Authorized project results can be exported as CSV or XLSX.

The current product truth supports CSV and XLSX export. ElTract does not claim additional export formats unless they are added to the product.

Yes. Automate supports workflow authoring, versions, runs, conditions and current actions for ElTract notifications and configured webhooks. Workflow execution requires the dedicated automation worker and runtime configuration.

Yes. Automate can send configured outbound webhooks as workflow actions and records destination/delivery state. This depends on the Automate runtime being configured and available.

ElTract Engage includes sender accounts, templates, drafts and manual/campaign/sequence outbox workflows. Delivery requires the trusted Engage runtime and a configured sender.

Google and Microsoft OAuth mail integrations are currently beta and require provider client configuration. SMTP sender support is implemented through the Engage runtime.

ElTract has a Node API used by the authenticated product application. Normal product API requests currently require a Supabase user access token plus active organization context. Generated ElTract API keys have a lifecycle but are not currently accepted as normal external endpoint authentication.

No. API keys can currently be created, listed and revoked, with hashed storage, but generated keys do not authenticate ordinary external ElTract API requests today.

Not as a current end-to-end capability. The product contains a truthful not-enabled MCP screen, but ElTract does not currently advertise MCP access as available.

Not currently. The product’s Ask ElTract control explicitly shows “Not connected” and does not fabricate an AI response when no provider is connected.

ElTract’s current crawling boundary is public web sources. Authenticated crawler browser sessions and a secure browser-session vault are not currently implemented.

No. Tracking pixels and open/click analytics are currently unavailable, and the marketing site does not present them as active Engage features.

No. Engage attachments are currently unavailable.

You can import CSV/XLSX into project data and use the Data Quality/enrichment foundation on product data. Monitoring itself is project/source based and requires the crawl runtime, so the exact monitoring workflow still needs a configured public source to revisit.

Manual copying usually ends with a disconnected snapshot. ElTract can keep project/run context, structured records, review state, import/export history, entity source evidence, Web Memory and selected monitoring or workflow actions connected to the same data.

The change is stored in monitor/change context and can appear alongside Web Memory and notifications. When Automate is configured, a monitor-change domain event can also be used as a workflow trigger for an ElTract notification or configured webhook.

Collect handles public sources, projects and extraction runs. Data handles structured results, imports, review, quality and exports. Leads maintains company and people context. Monitor revisits selected public sources and surfaces changes. Automate connects supported triggers to notifications or webhooks. Engage manages configured outreach workflows and sender delivery.