Request this connection

Kit + Custom API

Kit and Custom API are listed as a possible connection, but Kit needs a verified integration path. Ask us about the workflow you need.

Availability describes Plandalf's product, not your account's connection state.

Connection status

Know what is ready before you build

Each platform has its own setup path. A pair is only called a template when a published template exists.

Kit

Built for you in 24 hours

View Kit connections

Custom API

Webhook path available

View Custom API connections

This is a connection idea, not a shipped native pair. Tell us the event, destination action and fields you need before relying on it.

Triggers and actions

What Kit and Custom API can do

Provider capabilities and Plandalf steps are labelled separately. Ideas still need verification and a connecting workflow.

Kit

Triggers

  • Subscriber joinsIdea to verify

    Confirm whether the provider can emit this event or whether polling is needed.

Actions

  • Create or update subscriberIdea to verify

    Map the buyer email and consent before writing to the destination.

  • Apply a tag or groupIdea to verify

    Confirm the provider action and its account permissions.

Custom API

Triggers

  • Source eventIdea to verify

    Identify an event from Custom API that can be sent to a webhook.

Actions

  • Destination actionIdea to verify

    Confirm an API or manual action in Custom API before designing the workflow.

Workflow ideas

Kit and Custom API workflow matrix

Each row is a concrete workflow to evaluate. The pair status above tells you whether Plandalf already has a template or connector.

WorkflowTriggerActionWhat needs work
Subscriber joins → Destination actionKitSubscriber joinsCustom APIDestination actionA planning idea: verify both provider operations and the connecting step before relying on this workflow.
Source event → Create or update subscriberCustom APISource eventKitCreate or update subscriberA planning idea: verify both provider operations and the connecting step before relying on this workflow.

Worth handling by hand

  • Choose one identifier shared by Kit and Custom API, usually an email or provider record ID, before syncing records.
  • Test the event payload, retries and duplicate handling with real test records before launch.

More connections

More Kit workflow ideas

Compare another destination, its first operation to investigate, and whether a ready-made path exists.

Feature detail