Integrationsfolk

Send the leads you find and reach to folk.

Paste a folk API key once. The people in a table with the Send to folk column go into the folk group you pick, with that group's fields and their company, matched by email, and every reply lands on the person as an interaction.

  • ConnectA folk API key
  • DirectionGetSales to folk
  • Credits0
GetSales to folk

What GetSales sends to folk: a person into a folk group matched by email, with the group's custom fields and their company named on them, and a reply or a hand-off as an interaction on the person.

  1. Person to Person in a group

    matched by email, with the group's custom fields

  2. Company to Company on the person

    named on the person

  3. Reply or hand-off to Interaction

    on the person, the reply's text and its channel

What it does

What goes to folk,
and what stays

GetSales writes to your folk workspace and reads only what it needs to write well.

What GetSales sends

  • People

    Each person the Send to folk column sends, created or updated in the folk group you pick. The fields you map, nothing else.

  • Their company

    The person's company, named on the person, the way folk keeps it.

  • Replies and hand-offs

    When a person you sent answers on LinkedIn or by email, or the AI SDR hands the thread to your team, an interaction lands on the person.

What GetSales reads

  • Your groups and fields

    Your folk groups and each group's custom fields, so you map to your own.

  • The match

    The person with that email, so they are updated, not made again.

Not in this version

  • Pulling from folk

    folk groups do not come into GetSales. Export them to CSV and import the file into a table.

  • Deals and owners

    No deals, custom objects or owners.

  • New fields

    GetSales never creates a field in folk. Map to the group's own fields.

When it runs

Set it once,
it keeps sending

The Send to folk column works like every other column in a table.

  1. By hand

    Pick rows in a table and run the column on them.

  2. As rows land

    Switch on Auto-run and each new row is sent when it lands, or only the rows that meet your condition, such as an email found.

  3. From a workflow

    A workflow step runs the column for a person, for example after they reply.

What it costs

Nothing
per record

The writes run on your own folk workspace with your own key, so GetSales charges no credits for them. Finding a work email in the table is billed as it always is.

What a credit costs
A person sent
0
A reply logged as an interaction
0
A work email found in the table
Its own rate

Set it up

Connected
in five steps

  1. Make a key in folk

    In folk, open Settings, API and create an API key.

  2. Paste it in GetSales

    Open Settings, Integrations, folk, paste the key and save. GetSales tests it on save.

  3. Add the column

    In a people table, add the Send to folk column and pick the folk group the people go into.

  4. Map your fields

    Pick a folk field for each field you want to send, the group's custom fields included. Email is the match.

  5. Choose when it runs

    By hand, on every row that lands, or from a workflow step. Each cell shows the folk id, or the reason it was not sent.

API keys come with folk's Premium and Enterprise plans. A key works as the folk user who made it, so GetSales sees the groups that user can see.

Questions

folk,
your questions

Anything else, ask our AI sales agent.

Talk to AI Sales

How does the folk integration work?

You paste a folk API key in GetSales once, then add the Send to folk column to a people table and pick a folk group. Each person goes into that group with the fields you map and their company, matched by email. Replies on LinkedIn or by email and AI SDR hand-offs land on the person as interactions.

Which folk plan do I need?

Premium or Enterprise. folk's API, and with it the key GetSales needs, comes with those two plans only.

Does it log LinkedIn and email replies in folk?

Yes, for a person already sent to folk: their reply, on LinkedIn or by email, lands on the person as an interaction with its text and channel, and so does an AI SDR hand-off. The messages you send are not logged in this version.

Can I send to my group's custom fields?

Yes. Each folk group has its own custom fields, and the column maps to the fields of the group you pick. GetSales never creates a field in folk.

Will it create duplicates in folk?

A person is matched by email, so one already in folk is updated, not created again. A person with no email is not sent. folk also checks new people for duplicates and merges them on its side.

Is it a two-way sync?

No. GetSales sends to folk and reads only your groups, their fields and the people it matches. To work a folk group in GetSales, export it to CSV and import the file into a table.

Does sending to folk cost credits?

No. The writes run on your own folk workspace with your own key, so they cost no credits. Finding a work email in the table is billed at its own rate.

How do I disconnect folk?

Delete the key in Settings, Integrations, folk. GetSales deletes the stored key and the columns that send to it stop. To end it on folk's side too, delete the key in folk.

Your CRM, kept current

Every lead, in the right group.

Paste a key, pick a group, map once, and the people your tables find go into folk as they land.

Found in GetSales. Worked in your CRM.