Quick start

  1. Open After Networking from your CRM sidebar.
  2. Tap Scan to capture a card with your camera, or Upload Cards to choose images from your device.
  3. Review the extracted contact (name, email, phone, company, title) and tweak anything the AI got wrong.
  4. Hit Sync. The contact is created in your CRM with the tags and custom fields you've configured.
  5. Your follow-up workflow takes it from there — email, SMS, and tasks fire automatically.

How scanning works

When you submit a card image, the app sends it to our vision pipeline, which runs OCR on the card and extracts structured fields:

  • Name and title
  • Company
  • Email and phone
  • Website and LinkedIn URL when present

You'll see the extracted record next to the original photo so you can verify the result before syncing.

Tip: good lighting and a flat surface produce the best results. If the photo is blurry or angled, retake it before syncing.

Bulk upload

After an event you can drop a stack of card photos in at once.

  1. Click Upload Cards.
  2. Select up to 50 images at once (front and back of the same card count as one card).
  3. The app processes them in parallel and lists each result in the dashboard.
  4. Click Sync All to push every successful extraction to your CRM in one shot.

Duplicate detection

If you scan the same card twice — or if a contact with the same email or phone already lives in your CRM — the app will detect the match and merge new info into the existing record instead of creating a second one.

  • Matches are made on email first, phone second, and a name + company fuzzy match third.
  • Existing values are preserved by default; new fields fill in any blanks.
  • You'll see a Merged badge instead of Created on cards that were matched.

Custom field mapping

Out of the box, extracted values map to your CRM's standard contact fields. To send extra data — for example, the event name, the badge color, or a custom note — open Settings and add a mapping:

  1. Pick the source field (anything from the card, plus a few app-provided fields like scanned_at and event).
  2. Pick the destination CRM custom field.
  3. Save. New scans use the mapping automatically; existing scans aren't backfilled.

Workflows in GoHighLevel

Automations run inside GoHighLevel — not in After Networking

When you sync a card, GoHighLevel creates or updates a contact. To follow up automatically — for example, send a welcome email or queue a task — build a workflow in GoHighLevel. Workflows run on their own once the trigger conditions are met.

What workflows are

A workflow is an automated sequence of actions that starts when a trigger fires. They help you save time on follow-ups, reminders, and CRM updates without doing each step by hand.

Trigger

The event that starts the workflow — for example, Contact created, a form submission, or a tag applied.

Actions

What happens next: send email or SMS, create tasks, update fields, assign owners, and more.

How GoHighLevel expects you to build one

  1. Choose a trigger — In GHL, open Automation (workflows), click Add new trigger, and pick the event (for card syncs, Contact created is a common starting point).
  2. Refine with filters (optional) — Filters limit when the workflow runs. For contacts from this app, a tag filter keeps the automation scoped to the right people. Save the trigger when it looks right.
  3. Add actions — Click Add action and choose what should happen (email, SMS, task, etc.). You can chain several actions in one workflow.

Example: Email everyone from one expo

When you scan cards, tag each upload with the event name (for example techwest-2026 or whatever you typed as the tag in this app). That tag is how GoHighLevel knows they met you at that show — not another one.

In GoHighLevel, build one workflow per expo (or reuse a recipe and duplicate it): trigger Contact created, add a filter so the contact has that exact tag, then add a Send email action. Every synced contact who lands with that tag gets your follow-up; change the tag in the filter when you exhibit somewhere else.

Sample email (match the event in copy)

Subject: Great meeting you at TechWest 2026

It was great meeting you at TechWest 2026 — thanks for taking a card. [Add what you promised: calendar link, deck, coupon, etc.]

In the GHL email action, plug in merge fields so each contact sees their name; keep the expo name in the sentence so every send still references the event.

Swap TechWest 2026 for whatever expo name you use as the tag and in the message so the email always matches where you met them.

For publishing, testing, and troubleshooting (reentry, live tests, multiple triggers), see GoHighLevel's guide: Getting started with workflows.

LinkedIn integration

If a card includes a LinkedIn URL — or one is detected from the contact's name + company — the app can send a connection request without leaving the dashboard.

  • Connect your LinkedIn account once under Settings > Integrations.
  • Each card row shows a LinkedIn badge with the request status: queued, sent, or connected.
  • Requests respect LinkedIn's daily limits and are queued safely if you hit them.

Troubleshooting

"AI couldn't read this card"

Retake the photo with better lighting on a flat surface. Avoid glare from glossy cards. You can also edit the fields by hand and sync.

"Sync failed"

Open the card and check the error banner. The most common cause is a missing required field in your CRM. Fill it in and click Retry sync.

"My follow-up sequence didn't start"

Sequences fire from your CRM, not from After Networking. See also Workflows in GoHighLevel for how to wire triggers and tags. Double-check the trigger that watches for new contacts (or for the tag the app applies) is enabled.

Still stuck?

Drop us a line at /contact — we read every message.