Overview
Monorepo for @absolutejs/engagement sales-engagement adapters.
Engagement Adapters
engagement-adaptersworkspacealphaCommerce & GrowthMonorepo root for @absolutejs/engagement sales-engagement adapters — enrichment + outreach activity from Apollo, Outreach, Salesloft, … normalized to the EngagementSource contract. Subpackages live in ./<name>/ and publish independently as @absolutejs/engagement-<name>.
#Installation
BASH
git clone https://github.com/absolutejs/engagement-adapters.git#Capabilities
Overview
Monorepo for @absolutejs/engagement sales-engagement adapters.
A sales-engagement platform (Apollo, Outreach, Salesloft, …) is two things at once: an enrichment source (who is this person / company) and an activity source (what outreach has actually happened — emails sent, opened, replied; LinkedIn touches; calls). Each adapter normalizes one provider to the single EngagementSource contract so a consuming app can pull both without knowing which vendor is behind it.
Packages
Package — Provider — Publishes as
core/ — the EngagementSource contract + normalized types — @absolutejs/engagement
apollo/ — Apollo.io — @absolutejs/engagement-apollo
Show 1 more
Add a provider by dropping a new .// workspace that implements EngagementSource and publishes as @absolutejs/engagement- — same shape as every other adapter monorepo in the ecosystem (dataset-adapters, queue-adapters, voice-adapters, …).
Why it exists
The point isn't "another enrichment vendor" — we already have those. It's that a rep's real outreach activity lives in these platforms, and that activity is what tells you which deals to keep driving and which to let cool. Pulling it onto a unified deal timeline is the value.
Repository composition
2 public packages and 0 private workspace projects are versioned and developed together.
Outcomes
What you can build
Packages
Package — Provider — Publishes as
Why it exists
The point isn't "another enrichment vendor" — we already have those. It's that a rep's real outreach activity lives in these platforms, and that activity is what tells you which deals to keep driving and which to let cool. Pulling it onto a unified deal timeline is the value.
Hardening checklist
Production guidance
Make every external boundary explicitPin the deployed engagement-adapters version, replace example or memory-backed dependencies with durable implementations, bound external calls, protect credentials, and emit enough evidence to retry or recover safely.
Follow in order
Troubleshooting path
1
Trace from the first failed boundary
Reproduce the smallest canonical engagement-adapters example, confirm the supported entry point and version in the API explorer, then inspect the first boundary that did not produce its documented result.
#Workspace contents
2 public packages and 0 private workspace projects are maintained in this repository.
@absolutejs/engagementv0.0.8
Public package — The EngagementSource contract + normalized types for @absolutejs/engagement sales-engagement adapters — enrichment (person/company) and outreach activity (email/LinkedIn/call touchpoints).
@absolutejs/engagement-apollov0.0.8
Public package — Apollo.io EngagementSource adapter for @absolutejs/engagement — person/company enrichment and outreach activity (emails sent/opened/replied) from the Apollo API.
Workspace project
This workspace project is not published as a standalone npm package. Use its repository and the accurately labeled public or private workspace contents below.