Pipeliner

Connect Pipeliner to send enquiries to the records your team manages. You need access to configure the form in Craft and credentials for the destination account. The steps below establish the connection; finish by sending a test submission to verify the result.

Step 1. Create the Integration

1. Navigate to Formie → Settings → CRM.
2. Click the New Integration button.
3. Select Pipeliner as the Integration Provider.

Step 2. Connect to the Pipeliner API

1. Go to Pipeliner and login to your account.
2. In the top main menu, click on Menu icon in the far-left of the screen (9 dots).
3. In the top sub-menu, click on the Obtain API Key.
4. Copy the API Token from Pipeliner and paste in the API Token field in Formie.
5. Copy the API Password from Pipeliner and paste in the API Password field in Formie.
6. Copy the API Space ID from Pipeliner and paste in the API Space ID field in Formie.

Step 3. Test Connection

1. Save this integration.
2. Click on the Refresh button in the right-hand sidebar.

Step 4. Form Setting

1. Go to the form you want to enable this integration on.
2. Click the Integrations tab.
3. In the left-hand sidebar, select the name you gave the integration.
4. Choose the data objects (record types) you want to use, and enable their mapping options where available.
5. Map the required destination fields using the variable picker. Follow the requirements shown for each selected record type.
6. Enable the integration.
7. Click Save to save the form.

For a contact enquiry, map the visitor’s email and name where those fields are available.

Verify a Submission

Save the form, open it on your site and submit recognisable test values. Find the test record in the selected CRM destination. Check the mapped values and whether the integration created a record or updated an existing one as intended.

If nothing arrives, check whether integration conditions matched, whether the submission was complete and non-spam, and whether Craft’s queue has processed the job. A successful connection check verifies credentials; it does not prove that field mapping and delivery work. See Connect and Test an Integration for a complete mapping and verification workflow.