Skip to main content

What it does

Connecting Typeform gives you a Form Submitted trigger: every time someone completes one of your forms, Custral receives the response and can act on it: create or update a record, start a sequence, assign a task, or open a conversation. Use it when your forms already live in Typeform. If you don’t have that investment, Custral’s own forms write straight to your objects with no integration to maintain.

Connect

1

Authorize Typeform

Go to Settings → Integrations, choose Typeform, and complete the OAuth consent screen with the Typeform account that owns the forms.
2

Grant form access

Custral requests forms:read and forms:write. Read to receive responses and list your forms, write to register the delivery hook on the form you pick.
3

Build a workflow on the trigger

In Workflows, add a trigger, choose Typeform → Form Submitted, and pick which form fires it.

Configure

Map the form’s answers onto your schema in the workflow’s action step, each Typeform field becomes a variable you can drop into a create-record or update-record action. A field you don’t map is simply ignored.
Map the respondent’s email onto an Email property. That’s what lets Custral match the submission to an existing contact instead of creating a duplicate, and what lets replies thread back to the same person.

Resources synced

Limitations

  • The integration is inbound only: Custral reacts to submissions but doesn’t create or edit Typeform forms.
  • Only submissions that arrive after you connect fire the trigger. Existing responses aren’t backfilled, export and import those instead.
  • File-upload answers arrive as links to Typeform, not as File properties.

Troubleshooting

Disconnect

Disconnect from Settings → Integrations. Workflows built on the trigger stop firing but are preserved, reconnecting the same account resumes them. Records already created stay.

See also

  • Forms: Custral’s built-in forms.
  • Workflows: acting on the trigger.