Turn Customer Form Submissions into Immediate Action

Created by Advaith R, Modified on Wed, 5 Aug at 7:11 PM by Advaith R

  • Plan Availability
  • Essential
  • Standard
  • Premium
  • Enterprise

Customer form responses often provide the information teams need to continue onboarding, complete configurations, approve requests, or begin the next stage of a project. When team members must manually check individual projects for new responses, important submissions can go unnoticed and delay the work that follows.

You can create a form automation that notifies the appropriate internal team members as soon as a customer submits a response. The email can alert recipients to review the form in Rocketlane or include selected response data directly, helping teams act on customer inputs sooner and maintain consistent handoffs across projects.

What this workflow helps you achieve

This workflow helps teams:

  • Respond to customer submissions without waiting for someone to check the project.
  • Route form completions to the team members responsible for the next step.
  • Reduce delays caused by missed or unnoticed responses.
  • Include important customer information directly in the notification email.
  • Apply a consistent follow-up process across projects created from the same template.

How it works

The automation uses New form response as the trigger and Send email as the action.

You can configure the email in two ways:

Email typeHow it works
Completion notificationThe recipient receives an email confirming that the form was submitted and can open Rocketlane to review the responses.
Email containing response dataForm questions are mapped to project or task fields. The mapped fields are then added to the email using SmartFill.
NoteSmartFill cannot directly reference individual form question responses. To include a response in the email, map the form question to a corresponding project or task field.

Before you begin

Ensure that:

  • The form has been added to the relevant project template.
  • The internal recipient who should receive the email has been identified.
  • Any responses that must appear in the email are mapped to project or task fields.

If the email only needs to notify the recipient that the form was completed, field mapping is not required.


Step 1: Map form questions to fields

Complete this step only if the email needs to contain the submitted responses.

  1. Go to Templates.
  2. Open the relevant project template.
  3. Add Form task and select the form.
  4. Open the form question whose response should appear in the email.
  5. Map the question to the appropriate project or task field (in its Form template).
  6. Repeat this process for each response you want to include.
  7. Save the form.

When the customer submits the form, the submitted values are automatically added to the mapped fields.

NoteCreate or identify the required project and task fields before mapping the form questions.

Step 2: Add an automation to the form

  1. From the project template.
  2. Select the relevant form.
  3. Click Add Automation > Blank State.
  4. Select New form response as the trigger.

The automation will run whenever a customer submits a new response to that form.


Step 3: Configure the email action

  1. Add Send email as the automation action.
  2. Select the internal team member or members who should receive the email.
  3. Enter the email subject and message.
  4. If required, use SmartFill {{ to add the mapped project or task fields to the email body.
  5. Save the automation.

For a simple completion notification, the email can inform the recipient that the form was submitted and ask them to open the project to review it.

If the email must contain response data, add the corresponding mapped fields through SmartFill.


Example

A customer submits an onboarding form containing the following questions:

  • Preferred launch date
  • Primary contact
  • Implementation requirements

Each question is mapped to a corresponding project field. The email automation then uses SmartFill to include those project fields in the message.

The internal recipient could receive an email similar to:

Subject: Onboarding form submitted for [Project Name]

The onboarding form has been submitted.

  • Preferred launch date: [Launch Date]
  • Primary contact: [Primary Contact]
  • Implementation requirements: [Requirements]

Open the project in Rocketlane to review the complete response.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article

Contact our support team

Have more questions? Paid users can log in and email or chat with us.

Start your free trial