Form submission to CRM to email sequence

How to wire a contact form into a CRM record and an automated email nurture in one pass

A contact form that lands in an inbox is a lead stuck in a queue. A contact form wired to a CRM and an email sequence is a lead that receives a relevant response within minutes, gets logged in a system your team can act on, and enters a follow-up cadence that does not depend on someone remembering to send an email.

This recipe wires all three: the SGEN form, the CRM contact creation, and the email sequence trigger. By the end, every submission from the form automatically creates or updates a CRM contact and enrolls the contact in the first email in the sequence.

What is this for?

Use this recipe for any form where the submission represents a lead — someone who has expressed intent and who you want to follow up with in a structured way:

• Contact forms on service pages or consultation request pages.
• Lead magnet download forms — the visitor submits their email to receive a guide, checklist, or tool.
• Demo request forms — the visitor wants to see the product; the CRM record tracks the request and the email sequence confirms and prepares them.
• Free trial or plan upgrade inquiry forms — the submission signals purchase intent.

The recipe is not limited to a single CRM or email platform. SGEN's form integration layer supports multiple CRM and email providers. The setup pattern is the same regardless of which provider you use — only the field names differ.

Good use cases

Service business contact form. A visitor submits a consultation request. Within 2 minutes they receive an acknowledgment email confirming receipt and setting expectations ("we will respond within one business day"). The CRM contact record is created with the form data attached, and the sales team sees the new lead in their pipeline view.

Lead magnet download. A visitor submits their email to download a resource. The CRM record is created. The email sequence delivers the resource link in the first email, then sends a follow-up 3 days later with related content, and a third email 7 days later with a soft CTA.

Demo request flow. A visitor requests a product demo. The CRM record is tagged "demo-requested." The email sequence confirms the request and provides scheduling options. The sales team receives a notification from the CRM when the lead opens the email.

Webinar registration. A visitor registers for a webinar. The CRM creates the contact record with the event tag. The email sequence sends a confirmation, a reminder 24 hours before, and a recording link after the event.

What NOT to use this for

• Transactional emails for orders or bookings. Order confirmation, receipt, and booking confirmation emails are sent by SGEN's commerce or booking modules directly — they are not part of the CRM-driven nurture sequence. Do not route commerce-triggered flows through this recipe's setup.
• Mass broadcast emails to your entire list. This recipe is for the per-submission trigger that enrolls one contact at a time. For broadcasting to a segment of your existing CRM contacts, use the email broadcast tool in your CRM or email platform directly.
• Replacing a dedicated marketing automation platform for complex sequences. SGEN's native email sequence tools handle linear cadences well. If your sequence requires complex branching (if opened → branch A; if not opened after 3 days → branch B → branch C with conditions), a dedicated marketing automation platform is the right tool for the sequence logic, and SGEN pushes the contact to it via the integration.
• Collecting sensitive personal data in unencrypted forms. SGEN forms are encrypted in transit, but if you are collecting health, financial, or other regulated personal data, confirm your compliance requirements before routing through a CRM integration.

How this connects to other features

• Forms — the full form builder reference. Create and configure the form before starting this recipe.
• Automations — the automation engine that handles the CRM push and email sequence trigger. This recipe uses automations extensively.
• Email — the email sending surface. Templates, from-addresses, and sending domain settings live here.
• Newsletter signup flow — a simpler version of this recipe for pure subscription flows without CRM integration.
• Lead magnet funnel — a companion recipe for the download-gated lead capture variation of this flow.

Before you start

Have the form already built. This recipe assumes you have a form in SGEN with at least name and email fields. The form does not need to be published yet — it needs to exist with its fields defined. If you have not built the form, complete the Forms guide first, then return here.

Know which CRM you are integrating. SGEN connects to multiple CRM providers. Identify which CRM your team uses and confirm it is connected under SG-Admin → Settings → Integrations. If it is not connected, connect it first — the integration requires your CRM API credentials.

Have the email sequence copy ready (or at least the first email). The email sequence configuration requires at least the subject line and body for each email in the sequence. You can draft the emails after setting up the integration, but having at least the first email ready lets you complete the setup and test in one session.

Confirm your sending domain is verified. Emails sent from SGEN need to come from a verified sending domain to avoid spam folders. Go to SG-Admin → Settings → Email → Sending domains and confirm your domain shows as Verified. If not, complete the domain verification before setting up the sequence.

Where to go

The integration setup spans three areas of the admin:

1. SG-Admin → Forms — to confirm the form fields and find the form ID you will use as the automation trigger.
2. SG-Admin → Automations — to create the automation that pushes to the CRM and triggers the email sequence.
3. SG-Admin → Email — to create or confirm the email templates used in the sequence.

Start in Forms, then move to Automations, then Email.

Steps — Wire the form, CRM, and email sequence

1. Confirm your form fields and note the form ID

Go to SG-Admin → Forms. Open the form you are using for this flow. Confirm:

• The form has a field mapped to email (field type: Email, required).
• The form has a field mapped to name (field type: Text, required).
• Any additional fields you want to push to the CRM (phone, company, message) are present and labeled clearly.

Note the form ID from the URL: when you open the form in the admin, the URL contains the form ID (for example, /sg-admin/forms/edit/42 — the ID is 42). You will need this to configure the automation trigger.

2. Create the email templates for the sequence

Before building the automation, create the email templates you will use in the sequence. Go to SG-Admin → Email → Templates and click New template for each email in your sequence.

For a standard 3-email lead nurture:

• Email 1 — Acknowledgment (send immediately): Subject: "We received your message." Body: confirms receipt, sets a response time expectation, and gives the contact one useful thing (a resource, a relevant case study, or a clear next step) so the immediate email is not empty.
• Email 2 — Follow-up (send 3 days later): Subject: "[First name], a quick follow-up." Body: expands on the topic from the form context, shares one piece of relevant content, and restates the CTA (book a call, reply to this email, explore a resource).
• Email 3 — Last touch (send 7 days after email 2): Subject: "Still thinking it over?" Body: soft close — restate the value, acknowledge they may not be ready, and leave a low-commitment door open (reply when ready, here is how to book when the time is right).

Save each template before moving to the automation setup.

3. Create the automation — trigger on form submission

Go to SG-Admin → Automations and click New automation. Set:

• Trigger: Form submission.
• Form: select the form by name or ID from step 1.
• Condition (optional): if you want to filter submissions (for example, only trigger when the "How can we help?" field contains "consulting"), add a condition here. Leave blank to trigger on all submissions.

Name the automation clearly: Contact form → CRM + email sequence or similar. Save the trigger step before adding actions.

4. Add the CRM push action

In the automation editor, add an action step after the trigger:

• Action type: CRM — Create or update contact.
• Integration: select your connected CRM.
• Field mapping: map form fields to CRM contact fields.

Standard mapping for a name + email + message form:

Enable Create or update mode (not create-only): if the CRM already has a contact with this email, update the existing record rather than creating a duplicate. Duplicate contacts are one of the most common CRM data quality problems — the "create or update" setting prevents it at the point of entry.

5. Add the email sequence send actions

In the automation editor, add email send action steps after the CRM push:

Action 2 — Send Email 1 immediately:

• Action type: Send email.
• Template: select the acknowledgment template from step 2.
• Delay: none (send immediately after form submission).
• Recipient: {{form.email}}.

Action 3 — Wait 3 days:

• Action type: Wait / delay.
• Duration: 3 days.

Action 4 — Send Email 2:

• Action type: Send email.
• Template: select the follow-up template.
• Recipient: {{form.email}}.

Action 5 — Wait 7 days:

• Action type: Wait / delay.
• Duration: 7 days.

Action 6 — Send Email 3:

• Action type: Send email.
• Template: select the last-touch template.
• Recipient: {{form.email}}.

Save after adding each step. The automation editor shows a preview of the full sequence with timing.

6. Run the end-to-end test

Before activating the automation, run a test submission with a real email address you control:

1. Open the form on your staging site (or use the admin preview mode if staging is not available).
2. Submit the form with your test email address and accurate test data.
3. Within 2 minutes, confirm the acknowledgment email arrives in your test inbox. Check subject line, from address, personalization tokens, and links.
4. Log into your CRM and confirm the test contact was created with the correct field values.
5. Confirm the contact has the "contacted-via-form" tag.
6. Check the automation log in SG-Admin → Automations → [your automation] → Logs to confirm the run shows all steps as Completed with no errors.

Do not activate the automation until all six checks pass. A partial failure (CRM push succeeds, email fails) is still a failure — the contact has a broken experience.

What success looks like

• Every form submission creates or updates a CRM contact within 60 seconds.
• The acknowledgment email reaches the submitter's inbox within 2 minutes with correct personalization.
• The follow-up email sends on day 3 and the last-touch on day 10 without manual intervention.
• The CRM contact record is complete: name, email, source tag, submission date, and message note.
• The automation log shows no errors for the first 10 live submissions.

What to do if it does not work

Acknowledgment email goes to spam. The sending domain is not fully verified or the from-address domain does not match the sending domain. Go to SG-Admin → Settings → Email → Sending domains and confirm SPF, DKIM, and DMARC records are all showing as Verified. If any record is pending, wait 24 hours for DNS propagation and recheck.

CRM contact is not created. Check the automation log for the specific error. Common causes: CRM API credentials expired (re-authenticate the integration under Settings → Integrations), the CRM's contact creation API returned a rate-limit error (submissions are queued and will retry), or the email field value was blank (a form validation rule should prevent this, but check if the field is required).

Personalization tokens appear as literal text. The template contains {{first_name}} and the email body shows {{first_name}} to the recipient. This means the token is not resolving — the form field label in SGEN and the token name in the email template do not match. In the automation's email send step, confirm the field mapping: the token must match the field identifier exactly, not the display label.

Duplicate CRM contacts appear. The automation is set to "create only" instead of "create or update." Go to the CRM push step in the automation and change the duplicate handling to "create or update." For contacts that are already duplicated, use your CRM's merge tool to clean them up.

Follow-up email does not send on day 3. Check the automation log — if the contact unsubscribed from your email list before day 3, the sequence correctly stops (unsubscribes are respected). If the log shows the send step as Pending past day 3, the delay step may have a configuration error — confirm the unit is "days" and not "hours."

Form submissions are creating CRM contacts but not triggering the email sequence. This usually means the automation was saved with the email send steps in Draft status individually. In the automation editor, confirm each email send step shows as Active, not Draft. The automation overall can be active while individual steps are still in draft.

Reference — Field token quick-reference

When writing email templates for this automation, use these tokens to personalize content from the form submission:

If a token resolves to blank (the field was optional and the visitor left it empty), the email renders with the blank space. For optional fields, use conditional blocks in the template so the sentence restructures gracefully when the field is empty.

Anti-patterns to avoid

Sending the acknowledgment email more than 5 minutes after submission. A slow acknowledgment signals that the process is manual and slow. The immediate send is a trust signal — it proves the form worked and that the submitter's message was received. Any delay longer than 5 minutes degrades that trust signal.

Using "noreply" as the from-address. A "noreply" from-address tells the contact not to reply. For a lead nurture sequence where the goal is a conversation, this is the opposite of what you want. Use a real, monitored inbox as the from-address.

Not mapping the submission message to the CRM. The message field on the contact form is often the most valuable data the lead provides — their specific question or context. If it is not mapped to the CRM note, your sales team loses that context before they ever open the contact record.

Activating the automation before the end-to-end test. The automation processes every live submission from the moment it is activated. Activating an untested automation and discovering a bug after 50 submissions have gone through means 50 leads received a broken experience. Test first, activate after all checks pass.

Reference — Sequence performance benchmarks

After the automation has been running for 30 days with at least 50 submissions, review these metrics to assess whether the sequence is performing:

Track these from the email platform's analytics and the CRM's contact source report. If email 2 and 3 open rates are low, the primary fix is usually a better subject line — not a longer wait or more emails.

Reference — Scaling the sequence for different form types

The 3-email cadence in this recipe is a starting framework. Adjust timing and count based on the conversion context:

For consultation and demo requests where speed matters, consider adding a notification step before the acknowledgment email: Action 0 — Send internal notification (email your sales inbox with the lead details). This lets a human follow up before the automated sequence finishes, which outperforms the automated sequence for high-value leads.

Reference — Automation troubleshooting log template

When an automation run fails, log it in a short troubleshooting record. This creates a pattern history that makes future issues easier to diagnose.

Date: 2026-05-27Automation: Contact form → CRM + email sequenceSubmission: test@example.comStep that failed: Email send (Email 1)Error from log: SendGrid rate limit exceededResolution: Waited 15 minutes, re-triggered manually. Passed.Root cause: Peak submission window hit SendGrid limit. Increase limit or stagger sends.Follow-up action: Submitted request to increase SendGrid daily send limit.

A three-month log of automation failures is often the evidence needed to justify a plan upgrade or integration change — it turns "it broke once" into "it broke seven times in three months during our peak hours."

Related resources

• Forms — the full form builder reference. Build and configure the form before setting up this integration.
• Automations — the automation engine documentation. The trigger, CRM push, and email send steps in this recipe are all automation actions.
• Email — the email panel where templates, sending domains, and from-address configuration live.
• Newsletter signup flow — a simpler version for subscription-only flows that do not require CRM integration.
• Lead magnet funnel — the download-gated lead capture variation with a different email sequence structure.

Checklist — form-to-CRM-to-email sequence live

Run through this before marking the integration as production-ready:

• [ ] Form fields confirmed: email (required), name (required), optional fields as needed.
• [ ] CRM integration connected and authenticated under Settings → Integrations.
• [ ] Sending domain verified under Settings → Email → Sending domains.
• [ ] Email templates created for all emails in the sequence.
• [ ] Automation trigger configured: Form submission, correct form selected.
• [ ] CRM push step configured: Create or update, all fields mapped, tag applied.
• [ ] Email send steps configured with correct templates and delays.
• [ ] Automation set to Draft status during setup.
• [ ] End-to-end test run with personal test email — all six checks passed.
• [ ] Automation set to Active status after test passes.
• [ ] First 10 live submissions reviewed in automation log — no errors.

All items checked: the form captures leads, the CRM logs them, and the email sequence follows up — automatically and correctly.