Files

T

Rashad Karanouh 4f1ffa0a96 fix(twenty-partners): coerce null fields in TFT opportunity import (#22017 )

## What

The TFT `HTTP Request` action POSTs `null` for empty fields (e.g.
`amountMicros:null`, `closeDate:null`). The import schema typed those as
`z.number()/z.string().optional()`, which reject `null` (it is not
`undefined`), so the endpoint returned `ok:false / invalid_input` before
any API call.

## Fix

A `dropNulls` preprocessor on the request schema converts `null`
(top-level or nested) to "field absent" before validation. Null optional
fields are simply omitted from the created opportunity; required `name`
still fails correctly if null. No schema-shape or behaviour-contract
change.

## Tests

Added a case feeding the failing payload shape (`amountMicros:null`,
`closeDate:null`) → `created:true` with `amount`/`closeDate` omitted.
42/42 unit pass, lint clean.

Patch bump `1.1.1 → 1.1.2`.

<!-- This is an auto-generated description by cubic. -->
<a
href="https://cubic.dev/pr/twentyhq/twenty/pull/22017?utm_source=github"
target="_blank" rel="noopener noreferrer"
data-no-image-dialog="true"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source
media="(prefers-color-scheme: light)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img
alt="Review in cubic"
src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>
<!-- End of auto-generated description by cubic. -->

2026-06-23 17:37:41 +04:00

src

fix(twenty-partners): coerce null fields in TFT opportunity import (#22017 )

2026-06-23 17:37:41 +04:00

.env.example

feat(twenty-partners): add partners app (#20792 )

2026-05-21 19:14:20 +00:00

.gitignore

feat(twenty-partners): add partners app (#20792 )

2026-05-21 19:14:20 +00:00

.nvmrc

feat(twenty-partners): add partners app (#20792 )

2026-05-21 19:14:20 +00:00

.oxlintrc.json

Add twenty-partners on internal ci apps (#21975 )

2026-06-22 21:08:40 +02:00

.yarnrc.yml

feat(twenty-partners): add partners app (#20792 )

2026-05-21 19:14:20 +00:00

package.json

fix(twenty-partners): coerce null fields in TFT opportunity import (#22017 )

2026-06-23 17:37:41 +04:00

README.md

Source app About description from README and improve internal app READMEs (#22012 )

2026-06-23 15:27:52 +02:00

tsconfig.json

feat(twenty-partners): marketplace v2 — Application-driven matching workspace (#21816 )

2026-06-23 05:53:00 +00:00

tsconfig.spec.json

feat(twenty-partners): add partners app (#20792 )

2026-05-21 19:14:20 +00:00

vitest.config.ts

Add twenty-partners on internal ci apps (#21975 )

2026-06-22 21:08:40 +02:00

vitest.unit.config.ts

feat(twenty-partners): submit-partner-application HTTP logic function (#21040 )

2026-06-02 10:35:28 +00:00

yarn.lock

fix(security): refresh undici across lockfiles (6.x → 6.27.0, 7.x → 7.28.0) (#21870 )

2026-06-19 19:15:47 +02:00

README.md

Twenty Partners

Turns the CRM into the operating system for the Twenty partner program: intake partner-eligible deals, match them to vetted marketplace partners, and track the matching pipeline end-to-end.

What's inside

Partner object — slug, status, availability, served geographies, languages spoken, deployment expertise, Calendly link, and last-match timestamp.
Opportunity extensions — match status, design-doc status, intro and relance timestamps, and a relation to the matched partner.
Automatic matching — when an opportunity is set to auto-match, the longest-idle available partner is assigned and the deal is marked matched; if none is available it is handed off for manual matching with an explanatory note.
Views — a waiting-for-match queue, a matching-funnel overview grouped by status, the partner index, and a log of matched deals, all surfaced in the sidebar.

Match status pipeline

matchStatus follows the deal lifecycle:

Status	Meaning
`TO_BE_MATCHED`	Default — deal entered, awaiting assignment
`MANUAL_MATCH`	Needs a human to pick a partner
`AUTO_MATCH`	Triggers automatic partner assignment
`MATCHED`	Partner assigned
`INTRODUCED_TO_A_PARTNER`	Customer intro sent
`WORKING_WITH_A_PARTNER`	Engagement underway
`IMPLEMENTING`	Active implementation
`WON`	Deal closed won
`RECONNECT_LATER`	Paused — reconnect in future
`LOST`	Deal closed lost