← All nodes
Parsing

Contact / VCard / ICS Parser

Reads contacts from vCard text, or events from calendar (.ics) text, held in a column: one row per contact or event.

When to use it

Use it to bring an address-book export or a calendar feed into a flow — to clean, de-duplicate or load contacts, or to list meetings.

In a pipeline

Settings

SettingTypeRequiredDefault or hint
ColumnselectYesSelect column…
Readsselect—vcard

Example

Two contacts from one vCard export

  • Column=Card
  • Reads=Contacts (vCard)
vCard text in a column
SourceCard
crm.vcfBEGIN:VCARD FN:Ann Lee N:Lee;Ann;;; TEL;TYPE=CELL:+1 555 0100 EMAIL:ann@example.com ORG:Harbour Foods END:VCARD BEGIN:VCARD N:Cole;Bob;;; EMAIL:bob@example.com END:VCARD
One row per contact
SourceFull NameFirst NameLast NamePhoneEmailOrganizationTitleAddress
crm.vcfAnn LeeAnnLee+1 555 0100ann@example.comHarbour Foods——
crm.vcfBob ColeBobCole—bob@example.com———

Bob has no FN line, so his full name is built from N.

Worth knowing

  • vCard 3.0 fields read: FN, N, TEL, EMAIL, ADR, ORG and TITLE. Several phones or emails are joined with "; ".
  • Calendar events give Summary, Start, End, Location and Description; 20261016T090000Z becomes 2026-10-16T09:00:00Z (time-zone names are not applied).
  • The text column is replaced by the contact columns, which are known up front, so pickers downstream show them at once.
  • A row with no BEGIN:VCARD (or BEGIN:VEVENT) block is kept once with blanks and counted.

Others in Parsing