All docs

Connector support

Updated . 7 min read.

This page is generated from the connector definitions in Formspring. It lists what each connector can send, which fields it accepts and how you can test it before relying on it.

A connector marked awaiting provider verification is built and tested against recorded responses only. It has not passed a live test in a real account, so it is off by default.

How to read the table

  • Objects are the records Formspring creates or updates in the other tool. Every one is sent from Formspring to the tool; nothing is read back unless the direction says otherwise.
  • Fields are the submission fields the connector can map. "Mapped fields" means every field you choose to map.
  • Reading changes back appears for connectors Formspring can also read from. By default that is a read-only sync: Formspring reads what changed and counts it, and nothing is written back to your submissions. A form record sync can opt in to apply provider changes to the linked submission. Change notifications are listed per connector; where the provider does not offer them per connection, Formspring reads on a schedule instead.
  • Test shows whether the integration page can check the connection, list the choices to select from (forms, tags, audiences, databases) and check your field mapping.

Connectors

ActiveCampaign

  • Status: Implemented
  • How it connects: url and key
  • Where it works: funnels
  • Actions: sync contact, tag contact, trigger automation
  • Objects: contact (push)
  • Fields: email, firstName, lastName, phone
  • Test: send a test delivery

Activepieces

  • Status: Implemented
  • How it connects: webhook url
  • Where it works: forms
  • Actions: forward payload
  • Objects: payload (push)
  • Fields: mapped fields
  • Test: send a test delivery

Airtable

  • Status: Implemented
  • How it connects: personal token
  • Where it works: forms
  • Actions: create record
  • Objects: record (push)
  • Fields: mapped fields
  • Reading changes back: read-only sync by default; a form record sync can opt in to two-way. Change notifications: registered and renewed for each connection.
  • Test: connection test, destination selection (airtable bases, tables of the configured base)

Discord

  • Status: Implemented
  • How it connects: webhook url
  • Where it works: forms
  • Actions: post message
  • Objects: message (push)
  • Fields: mapped fields
  • Test: send a test delivery

GitHub

  • Status: Implemented, awaiting provider verification (off by default)
  • How it connects: personal token
  • Where it works: forms
  • Actions: create issue, link issue, sync issue status
  • Objects: issue (both)
  • Fields: mapped fields
  • Test: send a test delivery

Google Sheets

  • Status: Implemented
  • How it connects: oauth
  • Where it works: forms
  • Actions: append row
  • Objects: spreadsheet row (push)
  • Fields: mapped fields
  • Test: send a test delivery

HighLevel

  • Status: Implemented
  • How it connects: oauth
  • Where it works: funnels
  • Actions: create contact
  • Objects: contact (push)
  • Fields: email, firstName, lastName, phone, companyName, address1, tags
  • Test: send a test delivery

HubSpot

  • Status: Implemented
  • How it connects: api key
  • Where it works: forms and funnels
  • Actions: upsert contact
  • Objects: contact (push)
  • Fields: email, firstname, lastname, phone, company, jobtitle, website, lifecyclestage, hs_lead_status
  • Reading changes back: read-only sync by default; a form record sync can opt in to two-way. Change notifications: not available for each connection, so Formspring reads on a schedule instead.
  • Test: connection test, typed field mapping

Jira

  • Status: Implemented, awaiting provider verification (off by default)
  • How it connects: api key
  • Where it works: forms
  • Actions: create issue, link issue, sync issue status
  • Objects: issue (both)
  • Fields: mapped fields
  • Test: send a test delivery

Jornaya LeadID

  • Status: Implemented
  • How it connects: api key
  • Where it works: funnels
  • Actions: forward lead id
  • Objects: lead id (push)
  • Fields: universal_leadid, email, phone
  • Test: send a test delivery

Kit

  • Status: Implemented, awaiting provider verification (off by default)
  • How it connects: api key
  • Where it works: forms and funnels
  • Actions: upsert subscriber, add to form, tag subscriber, unsubscribe subscriber
  • Objects: subscriber (push)
  • Fields: email, first_name
  • Test: connection test, destination selection (kit forms, kit tags), typed field mapping

Klaviyo

  • Status: Implemented
  • How it connects: api key
  • Where it works: funnels
  • Actions: upsert profile, track event, subscribe profile
  • Objects: profile (push)
  • Fields: email, phone_number, first_name, last_name, organization
  • Test: send a test delivery

LeadByte

  • Status: Implemented
  • How it connects: api key
  • Where it works: funnels
  • Actions: submit lead
  • Objects: lead (push)
  • Fields: email, fname, lname, phone1, address1
  • Test: send a test delivery

Linear

  • Status: Implemented, awaiting provider verification (off by default)
  • How it connects: personal token
  • Where it works: forms
  • Actions: create issue, link issue, sync issue status
  • Objects: issue (both)
  • Fields: mapped fields
  • Test: send a test delivery

Mailchimp

  • Status: Implemented
  • How it connects: api key
  • Where it works: forms and funnels
  • Actions: upsert subscriber
  • Objects: subscriber (push)
  • Fields: email, tags
  • Test: connection test, destination selection (mailchimp audiences), typed field mapping

Make

  • Status: Implemented
  • How it connects: webhook url
  • Where it works: forms
  • Actions: forward payload
  • Objects: payload (push)
  • Fields: mapped fields
  • Test: send a test delivery

Microsoft Teams

  • Status: Implemented, awaiting provider verification (off by default)
  • How it connects: webhook url
  • Where it works: forms
  • Actions: post message
  • Objects: message (push)
  • Fields: mapped fields
  • Test: connection test

monday.com

  • Status: Implemented
  • How it connects: personal token
  • Where it works: funnels
  • Actions: create item
  • Objects: board item (push)
  • Fields: name, email, phone, text, status, date
  • Test: send a test delivery

n8n

  • Status: Implemented
  • How it connects: webhook url
  • Where it works: forms
  • Actions: forward payload
  • Objects: payload (push)
  • Fields: mapped fields
  • Test: send a test delivery

Notion

  • Status: Implemented
  • How it connects: personal token
  • Where it works: forms
  • Actions: create page
  • Objects: database page (push)
  • Fields: mapped fields
  • Reading changes back: read-only sync by default; a form record sync can opt in to two-way. Change notifications: not available for each connection, so Formspring reads on a schedule instead.
  • Test: connection test, destination selection (notion databases shared with the integration), typed field mapping

Personio

  • Status: Implemented
  • How it connects: api key
  • Where it works: funnels
  • Actions: create applicant
  • Objects: applicant (push)
  • Fields: first_name, last_name, email, phone, message
  • Test: send a test delivery

Pipedrive

  • Status: Implemented
  • How it connects: api key
  • Where it works: funnels
  • Actions: upsert person, create deal
  • Objects: person (push), deal (push)
  • Fields: name, email, phone, org_name, title, deal_title, deal_value, deal_currency
  • Test: send a test delivery

Postmark

  • Status: Implemented
  • How it connects: api key
  • Where it works: forms
  • Actions: send email
  • Objects: email (push)
  • Fields: mapped fields
  • Test: send a test delivery

Recruitee

  • Status: Implemented
  • How it connects: api key
  • Where it works: funnels
  • Actions: create candidate
  • Objects: candidate (push)
  • Fields: name, email, phone, cover_letter, cv
  • Test: send a test delivery

Resend

  • Status: Implemented
  • How it connects: api key
  • Where it works: forms
  • Actions: send email
  • Objects: email (push)
  • Fields: mapped fields
  • Test: send a test delivery

Salesforce

  • Status: Implemented
  • How it connects: oauth
  • Where it works: funnels
  • Actions: upsert lead or contact, create opportunity
  • Objects: lead (push), contact (push), opportunity (push)
  • Fields: Email, FirstName, LastName, MobilePhone, Phone, Company, Title, LeadSource, Description
  • Test: send a test delivery

SendGrid

  • Status: Implemented
  • How it connects: api key
  • Where it works: forms
  • Actions: send email
  • Objects: email (push)
  • Fields: mapped fields
  • Test: send a test delivery

Slack

  • Status: Implemented
  • How it connects: webhook url
  • Where it works: forms
  • Actions: post message
  • Objects: message (push)
  • Fields: mapped fields
  • Test: connection test

Stripe (customer capture)

  • Status: Implemented
  • How it connects: api key
  • Where it works: forms
  • Actions: create customer
  • Objects: customer (push)
  • Fields: email, name
  • Test: send a test delivery

Telegram

  • Status: Implemented
  • How it connects: api key
  • Where it works: forms
  • Actions: send message
  • Objects: message (push)
  • Fields: mapped fields
  • Test: send a test delivery

TrustedForm

  • Status: Implemented
  • How it connects: api key
  • Where it works: funnels
  • Actions: validate certificate
  • Objects: certificate (push)
  • Fields: xxTrustedFormCertUrl, email, phone
  • Test: send a test delivery

Zapier

  • Status: Implemented
  • How it connects: webhook url
  • Where it works: forms
  • Actions: forward payload
  • Objects: payload (push)
  • Fields: mapped fields
  • Test: send a test delivery

Zoho CRM

  • Status: Implemented
  • How it connects: oauth
  • Where it works: funnels
  • Actions: create lead
  • Objects: lead (push)
  • Fields: Email, First_Name, Last_Name, Phone, Mobile, Company, Lead_Source, Description
  • Test: send a test delivery