Skip to main content
Pro plan. folk works through a connection and HTTP steps, which are part of Pro and Agency (and the free trial). Anything you already have keeps working on every plan. See Plans and billing.
When a contact accepts or replies, a Webhook / HTTP step creates them in folk with their name, email and LinkedIn URL, in the group your team works from.
How it connects: folk’s public API with a bearer token. See folk’s Create a person docs. The request and answer below follow folk’s docs.

Before you start

  • folk plan: check folk’s pricing page for API access on your plan.
  • An API key: in folk, open Settings > API and create one.
  • The group’s id: folk’s API lists your groups and their ids (GET /v1/groups), or leave groups out.

1. Connect folk

In Kerux, open Integrations > Connections, click Connect on Custom API (under Developers):
  • How it signs in: Bearer token, paste the key.
  • Base URL: https://api.folk.app
Click Save, then Test connection.

2. Create the person

After Invitation accepted, add a Webhook / HTTP step named folk:
A contact without an email waits at this step: remove emails if you want everyone in folk. folk answers with the new person under data (trimmed):
Save {{steps.folk.response.body.data.id}} on the contact with an Update contact step (a custom field such as folk person id) to update the person later.

Test with one contact

In the Builder, click Test to open Test on one contact and check the person in the group in folk.

Common errors

The key is wrong or was deleted. Create a new one in Settings > API.
The group id doesn’t exist in this workspace. List your groups and copy the id again.
Creating doesn’t check for duplicates. Save folk’s id on the contact and update instead of creating on later runs.
Related: Webhook steps, Attio, Notion.