ACTION_ID: cloudtalk_add_contact
NAME: Cloudtalk : Add Contact
CATEGORY: Outreach
CREDITS: 0

Add a contact to CloudTalk with its numbers, emails, tags and company
details, so the row becomes callable from the CloudTalk dialer.

PREREQUISITE: CloudTalk account connection — the user must create it in the Floqer UI
(Connections page); an agent cannot. Without it the action fails the row with
a connection / authentication error. Confirm it exists before configuring.

1. INPUTS

full_name (string, required)
  Full Name. The name of the contact

title (string, optional)
  Title. The title of the contact

company_name (string, optional)
  Company Name. The company name of the contact

industry (string, optional)
  Industry. The industry of the contact

website (url, optional)
  Website. The website of the contact

address (string, optional)
  Address. The address of the contact

city (string, optional)
  City. The city of the contact

zip (string, optional)
  Zip. Zip

state (string, optional)
  State. The state of the contact

country_id (string, optional)
  Country Id. The country Id of the contact

external_url (raw_array, optional)
  External Url. The external url of the contact

contact_numbers (string, optional)
  Contact Numbers. Numbers assigned to contact. Separate each number
  by a comma

email (email, optional)
  Email. Emails assigned to contact. Separate each email by a comma

contact_tags (string, optional)
  Contact Tags. Tags for contact. Separate each tag by a comma

contact_attribute (raw_array, optional)
  Contact Attribute. Contact Attribute

2. OUTPUTS

status (string) — Status/Response of the request

3. HOW TO CONFIGURE

No dynamic dropdowns — every field is a plain value or a
`jsonArray`. Configure Action body:

{
  "inputs": {
    "full_name": "{{input.full_name}}",
    "title": "{{enrich_person_linkedin_profile_01ab.person_current_job_title}}",
    "company_name": "{{input.company_name}}",
    "website": "{{input.company_domain}}",
    "contact_numbers": "{{person_enrich_by_floqer_01cd.phone_number}}",
    "email": "{{person_work_email_waterfall_01ef.work_email}}",
    "contact_tags": "floqer,inbound",
    "contact_attribute": [
      { "name": "Segment", "value": "{{input.segment}}" }
    ]
  }
}

Field-by-field:
  - full_name         The only required field.
  - contact_numbers   Comma-separated list — CloudTalk stores each as a
                      separate number on the contact.
  - email             Comma-separated list, same rule as the numbers.
  - contact_tags      Comma-separated list of tag names.
  - country_id        CloudTalk's numeric country ID, not an ISO code.
  - external_url /    `jsonArray` fields; each item is an object stored
    contact_attribute verbatim on the contact.

4. KEY NOTES

- `contact_numbers`, `email` and `contact_tags` are all comma-separated
  strings, not arrays — passing a JSON array stores a single malformed
  value.
- `country_id` expects CloudTalk's internal numeric country identifier.
  Leave it empty unless you already have that ID; an ISO code like `US`
  is not accepted.
- The action returns only a `status` string — no CloudTalk contact ID,
  so it cannot be chained into a later CloudTalk update.
- Duplicate protection is CloudTalk-side. Calling this twice for the
  same person can create two contacts; gate with a `filter` if you
  re-run rows.

5. WHERE IT FITS IN A WORKFLOW

Pattern: person_enrich_by_floqer -> filter (phone_number is not empty)
-> cloudtalk_add_contact. Terminal step — nothing downstream can consume
its output.

6. WHEN TO USE

Use cloudtalk_add_contact when CloudTalk is the dialer and you want
enriched rows available to agents as callable contacts.

7. WHEN NOT TO USE

Need a Salesfinity calling list instead
  -> action-detail/salesfinity_add_contact.txt

Need the contact in a CRM rather than a dialer
  -> action-detail/hubspot_upsert_object.txt

Last updated: 2026-08-03.