Flodesk

Rekomi's Flodesk integration adds every approved affiliate as a subscriber to a Flodesk segment.

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls POST /v1/subscribers with email, first_name, last_name, and segment_ids: ["segId"]. The endpoint is upsert, re-syncing returns 200 with the updated subscriber.

Status is server-managed (read-only) in Flodesk's API; new subscribers default to active.

Finding your API key

In Flodesk:

1. Account → Integrations → Developer API.
2. Click Add API key. Copy the key.

Connecting Flodesk in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the Flodesk card.
3. Paste your API key. Click Connect.
4. Rekomi runs a test call against GET /v1/segments?per_page=1.

Tags

Flodesk has no tag concept; only segments. Rekomi ignores the tags array on subscribe. If you want tag-like behavior, create dedicated Flodesk segments and pin per-campaign overrides to them.

Referred customers and leads (optional)

Turn on Sync referred customers and leads on the integration page and every sale or lead Rekomi attributes to an affiliate is written to Flodesk as well, matched on email so existing contacts are updated, not duplicated. Each one carries:

• custom fields rekomi_referral_link, rekomi_campaign, rekomi_referring_affiliate, rekomi_referring_affiliate_code, rekomi_last_event, rekomi_last_sale_amount
• no tags; segment on rekomi_last_event
• Affiliates synced by the section above also get Rekomi referral link, Rekomi campaign and Rekomi affiliate status in the same fields, so you can merge a partner's link into your emails.

Refunded, denied and fraud-quarantined conversions are never pushed, and imported historical conversions are skipped. It is off by default. If your Flodesk plan does not allow creating custom fields by API, create them yourself with exactly these keys and Rekomi fills them.

When sync fires

• Default: only Approved affiliates sync.
• Optional: turn on "Include applicants before approval" to also sync Pending.

Per-campaign overrides

Each campaign can override the account-level configuration. From a campaign's detail page, open the Settings tab and scroll to the CRM sync for this campaign section.

Per-affiliate sync visibility

Open any affiliate's detail page. The CRM sync panel shows the per-CRM status. Resync clears prior jobs and re-fires the sync.

Troubleshooting

• 400 with "status is read-only", Should not happen; Rekomi never sends status. If you see this, contact support.
• 429, Flodesk throttles at 100 req/min on subscribers. No Retry-After header documented; Rekomi falls back to exponential backoff.
• Sync fails with 401/403 after working before, The API key was revoked. Rekomi marks the integration "action needed" and emails you a reconnect prompt once per breakage. Reconnect with a fresh key, then use Resync all on the Failed tile of the integration page.

Disconnecting

From the Flodesk connect page, click Disconnect. Integration row + per-campaign overrides are deleted. Sync history is preserved.

---

See the flodesk integration overview on the marketing site for use-cases, persona fit, and unique automation patterns.