What Context7 data does Well pull into Pennylane?

Well watches Context7 for attachments matching the configured invoice and receipt filters, extracts no structured financial records today; reachable over MCP as a connect-only surface, and forwards the structured output to Pennylane as supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR, with the original email message ID stored on every record for audit.

Will every Context7 record post to Pennylane automatically?

Not always. Within seconds of Context7 firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Pennylane email-in address and Pennylane drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

How does Well prevent duplicates when posting Context7 records to Pennylane?

Every Context7 message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Pennylane entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Pennylane.

Can I customise which Context7 fields are sent to Pennylane?

The default mapping turns every parsed Context7 attachment into a Pennylane-shaped record (vendor, amount, due date, tax). From the integration settings page you can adjust the parsing prompt, force a vendor mapping, attach the original PDF on a specific Pennylane field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Pennylane entries.

What happens if a Context7 record fails to post to Pennylane?

When a record fails to post to Pennylane (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Context7 record. Nothing silently drops.

How does Well authenticate with Context7 and Pennylane?

Context7's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and Context7 hosts outside the EU; Well processes records per the storage region configured for your workspace.

Context7 to Pennylane

AvailableNative · Context7Native · Pennylane

Connect Context7 to Pennylane with Well

Context7 attachments are parsed inside Well for vendor, amount, VAT, and due date, then the documents arrive at Pennylane as drafts with the original message ID attached.

Connect both toolsView all integrations

Context7

Source

Connect Context7 to Well over its MCP server so your agents can reach it, with no structured data sync.

Pennylane

Target

The Pennylane integration creates a bidirectional bridge between Well and your accounting workspace.

What is unique

Context7 is a developer documentation tool reached over MCP, not an accounting source, and this page does not pretend otherwise.

Connecting Context7 to Well opens an MCP connection so Context7 is reachable from the same workspace as Pennylane, but Context7 exposes no structured financial entity today: there is nothing to parse into an invoice and nothing to match against the Pennylane ledger. The point of the pairing is to have one connection surface and reach, not a document flow. Should Context7 expose a structured tool catalog in future, this pairing would become eligible for a real Pennylane data flow. Until then it is connect-only.

What Well does with Context7 invoices on the way to Pennylane.

01Featured

Capture supplier invoices from email

Well watches Context7 for attachments matching invoice patterns, extracts amount, VAT, supplier, and due date in Well, then forwards the PDF to Pennylane's email-in inbox. The original message ID stays on the document so the audit trail traces from Pennylane back to the email that delivered the invoice.

Route personal-card vs supplier receipts

Receipts arriving in Context7 from employee personal cards are kept on the expense-reimbursement path inside Well, while supplier invoices route to the supplier-bill path. The category is decided from the sender domain plus the invoice format, so the right document type lands at Pennylane rather than a mixed pile.

Resolve a new vendor from the invoice header

When an invoice arrives from a vendor Well does not recognise, the header (legal name, tax ID, bank IBAN) is parsed and a vendor record is proposed inside Well. The matched document is then forwarded to Pennylane with the proposed match so Pennylane's OCR can resolve it on arrival.

Catch missing attachments before delivery

If an Context7 invoice references a credit memo or a delivery note that did not arrive, Well flags the missing attachment inside its own queue and holds delivery until you forward the supporting document. Documents reaching Pennylane always carry their supporting paperwork.

5 signals and actions across Context7 and Pennylane

Create a supplier invoice in Pennylane
Well forwards the extracted PDF to Pennylane's supplier inbox; Pennylane creates the supplier invoice with amount, VAT, and date pre-filled.
Action·Invoice
Resolve a Pennylane supplier from the document
Pennylane's OCR resolves the supplier name from the PDF. You confirm or correct the match on first sight.
Action·Company
Attach the source document to the Pennylane record
The PDF Well forwards is stored as the source attachment on whichever invoice Pennylane creates from it.
Action·Document
Create a customer invoice in Pennylane
Well forwards the document to Pennylane's collections address; Pennylane creates the customer invoice with the same OCR pre-fill.
Action·Invoice
Resolve a Pennylane customer from the invoice
Pennylane reads the customer name off the outbound invoice for collections. You confirm on first sight.
Action·Company

Connect Context7 and Pennylane in three steps.

1
Connect Context7
Click Connect with Context7; Context7's MCP server handles authorisation through Dynamic Client Registration. Context7's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
2
Map your accounts
Well discovers the Context7 attachments matching your invoice pattern (no structured financial records today; reachable over MCP as a connect-only surface) and the the Pennylane Purchases tab and the customer-invoice collections list. Tune the parsing prompt once on the first ten records; Well saves the mapping and applies it to every subsequent attachment above 85% confidence.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Pennylane
Click Connect with Pennylane; Well's OAuth proxy handles Pennylane authorisation through Dynamic Client Registration. Pennylane's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First syncup to an hour

How Context7 and Pennylane stay secure with Well

Well connects to Context7 through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Context7 secret; the server refreshes its own tokens on each session. Well processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

MCP server authEU residency optionGDPR-aligned

Scopes Well requestsmcp.context7.com/mcp

Read Context7 records
Scoped to no structured financial records today; reachable over MCP as a connect-only surface. No access to anything else in your Context7 account.
granted
Deliver documents to your Pennylane inbox
Well forwards the extracted document to your Pennylane email-in address; Pennylane reads supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR from it and you review and post. No write credential to Pennylane is requested.
granted
Modify or delete Context7 records
Not granted. Context7 is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

Disconnect any time from Well settings or Context7’s admin panel.

Frequently asked questions about Context7 and Pennylane on Well

01What Context7 data does Well pull into Pennylane?: Well watches Context7 for attachments matching the configured invoice and receipt filters, extracts no structured financial records today; reachable over MCP as a connect-only surface, and forwards the structured output to Pennylane as supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR, with the original email message ID stored on every record for audit.
02Will every Context7 record post to Pennylane automatically?: Not always. Within seconds of Context7 firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Pennylane email-in address and Pennylane drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.
03How does Well prevent duplicates when posting Context7 records to Pennylane?: Every Context7 message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Pennylane entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Pennylane.
04Can I customise which Context7 fields are sent to Pennylane?: The default mapping turns every parsed Context7 attachment into a Pennylane-shaped record (vendor, amount, due date, tax). From the integration settings page you can adjust the parsing prompt, force a vendor mapping, attach the original PDF on a specific Pennylane field, or compute a tag from your connected data. Custom mappings are versioned so a change does not retroactively touch already-posted Pennylane entries.
05What happens if a Context7 record fails to post to Pennylane?: When a record fails to post to Pennylane (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Context7 record. Nothing silently drops.
06How does Well authenticate with Context7 and Pennylane?: Context7's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and Context7 hosts outside the EU; Well processes records per the storage region configured for your workspace.