PitchKraft Support

Website contacts

Connect website forms to PitchKraft: add new contacts, update existing contacts and append each new enquiry to their notes.

Bring website enquiries into PitchKraft

Connect your website contact form to PitchKraft so that new enquiries create contacts and repeat enquiries update existing contacts in your website’s dedicated list. Each website has its own API key, and PitchKraft creates a contact list with the same website name. Each enquiry can be retained as a new note against the relevant contact.

You can review website enquiries within the PitchKraft interface. Alerts for new enquiries appear at the top right of the page.

For website owners: create the API key below, then ask your website developer to connect the form using this guide. Generating a key alone does not connect your website form.

1. Create your website API key

  1. In PitchKraft, open Settings → General → Website contacts.
  2. Click Create API key.
  3. Enter the website name and generate the key.
  4. Copy the key from the popup. It is shown only once.
  5. Store it in your website server’s secret settings.

Keep your key private. Your browser form must send data to your own server, which then calls PitchKraft. Never embed the API key in browser JavaScript or HTML.

2. Connect your form from your server

When a visitor submits your form, your server should send a POST request to:

https://www.app.pitchkraft.ai/api/crm/website-contact

Include these headers:

Content-Type: application/json
X-Pitchkraft-Api-Key: YOUR_GENERATED_API_KEY

If you use a website builder or form plugin, your developer must configure a server-side integration that sends the headers and JSON body below. Do not paste the API key into a public page or an HTML widget.

3. Map your form fields

FieldRequired?Details
fullNameYes (or firstName and lastName)Full name; saved. Maximum 300 characters.
firstNameYes (or fullName)Contact’s first name.
lastNameYes (or fullName)Contact’s last name.
emailYesValid email address; saved. Maximum 320 characters.
companyNameNoCompany name; saved. Maximum 300 characters.
phoneNumberNoContact phone number.
messageNoEnquiry message to retain in the contact’s notes. Include the new message on repeat submissions.

Provide either fullName or both firstName and lastName.

Existing contacts: when the submitted email already exists in the same website list, PitchKraft updates that contact rather than creating a duplicate. A new enquiry note can be appended so earlier enquiries remain available.

4. Test the request with cURL or Postman

Import this cURL example into Postman, or run it in a trusted terminal. Replace YOUR_GENERATED_API_KEY with your website’s key. Test once with a new email address, then submit again with the same email and a different message to confirm that the contact updates and a new note is appended.

curl --request POST 'https://www.app.pitchkraft.ai/api/crm/website-contact' \
  --header 'Content-Type: application/json' \
  --header 'X-Pitchkraft-Api-Key: YOUR_GENERATED_API_KEY' \
  --data-raw '{
    "fullName": "Aamir Sheikh",
    "email": "aamir.test@example.com",
    "companyName": "Acme Ltd",
    "phoneNumber": "+919876543210",
    "message": "Please contact me"
  }'

After a successful test, check the contact in the list named after your website and review its notes. On the repeat test, verify that the same contact was updated, no duplicate was created and the new enquiry note was appended. Check new-enquiry alerts where applicable, then test through your website form to confirm the complete connection works.

5. Understand responses and fix errors

200 OK — contact created or updated

{"contactId":12345}

The contact ID above is an example. A successful repeat submission should refer to the existing contact and preserve its earlier notes while appending the new enquiry.

400 Bad Request — check the form fields

{"message":"Full name and email are required."}

Provide an email address and either fullName or both firstName and lastName. Invalid email, name length or company name length also returns 400. Check the field requirements above.

401 Unauthorized — check the API key

{"message":"Invalid API key."}

The key may be missing, invalid or replaced. Check the X-Pitchkraft-Api-Key header and ensure your server uses the current key.

Repeat submissions: an email already present in the website list should be handled as a contact update, not a duplicate-email error. If the API does return an error, record the status and investigate it rather than claiming the enquiry was saved.

6. Replace a lost key or rotate your key

  1. Open Settings → General → Website contacts.
  2. Find the website and click Regenerate key.
  3. Copy the new key and update your website server’s secret settings immediately.
  4. Test a submission with a new email address, followed by a repeat submission to verify updating and note history.

The old key stops working immediately. Requests using it will fail until your website server is updated. The contact list and its existing contacts remain unchanged.

Using WordPress? Connect your form with a plugin

WordPress form plugins with webhook support can make this setup straightforward, without building a custom integration. A webhook sends each form submission from your website to PitchKraft. Choose a plugin that supports POST requests, JSON, custom headers and field mapping.

Example: Contact Form 7 with CF7 Apps

CF7 Apps adds webhook settings to Contact Form 7. Check the provider’s current plan requirements before installing.

  1. Install and activate Contact Form 7 and CF7 Apps.
  2. Go to Contact → CF7 Apps → Dashboard and enable the Webhook app under Integrations.
  3. Edit your enquiry or subscription form. In its CF7 Apps panel, open Webhook. Configure this individual form rather than applying the integration to every form.
  4. Set the URL to https://www.app.pitchkraft.ai/api/crm/website-contact, the method to POST and the data type to JSON.
  5. In Request Headers, set Content-Type to application/json and X-Pitchkraft-Api-Key to your generated key. Keep the key in server-side plugin settings, never a public or hidden form field.
  6. Map the fields using the form-tag options below. Use {{fields}} as the Request Body so the mapped fields form the top-level JSON object.
  7. Save and submit your form using a new email address, then repeat with that address and a different enquiry message. Confirm the same contact is updated, the new note is appended and no duplicate is created. If it fails, review the response codes below.

Example form-field mapping

Add these tags to your Contact Form 7 form, or add the corresponding webhook: option to your existing tags:

[text* your-name webhook:fullName]
[email* your-email webhook:email]
[text your-company webhook:companyName]
[tel your-phone webhook:phoneNumber]
[textarea your-message webhook:message]
[submit "Send enquiry"]

For separate name fields, replace the full-name tag with:

[text* your-first-name webhook:firstName]
[text* your-last-name webhook:lastName]

Subscription forms use the same connection. Include an email address and either a full name or both first and last names; an email-only form does not meet the required fields.

See the CF7 Apps webhook instructions for the plugin’s settings and mapping options. This example applies those options to PitchKraft; test it on your own form before relying on it.

Need a hand? Our 24/7 support team can help you configure the connection and troubleshoot submissions. Contact support@pitchkraft.ai. Do not send your API key in a support message.

Connect your website platform

Use the route below for your existing website or form tool. Prefer a direct server-side connection to PitchKraft. Zapier is optional, not a PitchKraft requirement. The routes below are configuration approaches based on the providers’ documented features, rather than one-click PitchKraft integrations. Check your plan’s add-on and automation availability before starting.

Platform or form toolSuggested route
Contact Form 7Use the WordPress walkthrough above.
WPFormsWebhooks addon: send JSON directly to PitchKraft.
Gravity FormsWebhooks Add-On: configure a direct request.
Elementor FormsSmall WordPress server-side connector that sends directly to PitchKraft.
WixWix backend code that sends directly to PitchKraft.
SquarespaceCustom or embedded form connected to a separately hosted server endpoint.
WebflowForm webhook to your server or a serverless connector, then to PitchKraft.
ShopifyShopify Flow where the relevant trigger and HTTP action are available; otherwise a form app with suitable API settings or a server-side connector.
Custom websiteYour server sends the API request described in steps 1–6.

Settings used by every route

The final request to PitchKraft must use POST to https://www.app.pitchkraft.ai/api/crm/website-contact, with JSON and the X-Pitchkraft-Api-Key header. Map email and either fullName or both firstName and lastName. Optional fields are companyName, phoneNumber and message. Send these as top-level JSON fields, not inside a data or fields wrapper.

WPForms

  1. Install and activate the Webhooks addon. WPForms currently requires an Elite licence for this addon.
  2. Edit your form and open Settings → Webhooks. Enable webhooks.
  3. Enter the PitchKraft endpoint, select POST and JSON, and add your API key as a custom request-header value in the private settings. Do not put it in a hidden form field.
  4. Map the Request Body keys to your form fields using the names above, save and test.

WPForms webhook documentation.

Gravity Forms

  1. Activate the Webhooks Add-On, then open Form Settings → Webhooks → Add New.
  2. Set the PitchKraft endpoint, POST and JSON. Add the API-key header.
  3. Choose the fields to send and map their keys to PitchKraft’s field names. Save the feed and test a submission.

Gravity Forms webhook documentation. Check add-on access for your licence.

Elementor Forms

Preferred route: a small server-side WordPress connector. A developer can use Elementor’s form-submission hook or a custom form action to send directly to PitchKraft.

  1. Identify the specific form and its field IDs.
  2. Add a small site plugin using elementor_pro/forms/new_record or a custom form action. Restrict it to the intended form.
  3. Map the submitted fields to PitchKraft’s JSON keys and send the POST request from WordPress, adding the API-key header from private server settings.
  4. Keep existing email and submission-storage actions, handle unsuccessful requests, and test the saved contact and alert.

This requires developer setup, but no Zapier account. Elementor form hooks and custom form actions.

Wix

Preferred route: Wix backend code. Ask your developer to connect the form’s supported submission event, or a custom form, to a backend function.

  1. Store your PitchKraft API key in Wix Secrets Manager.
  2. Read the submitted name, email and optional fields in the backend and map them to PitchKraft’s JSON fields.
  3. Send the POST request from the backend with the API-key header. Never return the key to browser code.
  4. Handle validation and delivery errors, then test the complete form submission.

The implementation depends on your Wix form type; this is a developer integration, not a ready-made PitchKraft action. See Wix custom development and Secrets Manager.

Squarespace

Preferred route without an automation subscription: a custom or embedded form and a separately hosted connector. Squarespace does not run server-side code within its pages.

  1. Have your developer create a secure endpoint on your own server or serverless hosting.
  2. Add a custom or embedded form that submits to that endpoint. This may replace the native form block; it is not a direct setting for an existing Squarespace form.
  3. The endpoint validates the submission, maps the fields and sends the authenticated JSON request to PitchKraft. Keep the API key on that server.
  4. Test success and error messages, contact creation and any email notifications you need.

Hosting and development may have costs. If you want to retain supported native form or newsletter blocks without a custom form, Squarespace’s Zapier integration is an optional alternative. See Squarespace custom-code limitations and native form integration with Zapier.

Webflow

Preferred route: a form webhook to a small server-side connector.

  1. Ask your developer to create an endpoint on your server or serverless hosting, with the PitchKraft API key held in private settings.
  2. Add that endpoint as a webhook destination in your Webflow form settings.
  3. The connector verifies the incoming webhook, extracts the form values and maps them to PitchKraft’s top-level JSON fields. It then sends the authenticated POST request to PitchKraft.
  4. Test contact creation and error handling. Retain Webflow’s existing storage and notification destinations as required.

No Zapier account is needed for this route. Do not point a browser form action directly at PitchKraft or expose the API key in page code. See Webflow form settings and webhook developer guidance.

Shopify

  1. Choose a trigger supported by your form app or subscription workflow. A standard contact-form submission is not automatically a Shopify Flow trigger; check your form’s integration.
  2. If using Flow on a supported plan, add Send HTTP request, set POST and the PitchKraft endpoint, and configure the JSON body and headers.
  3. Store your PitchKraft key as a Flow secret and reference it in the API-key header. Map the contact fields, then test.

The HTTP action currently requires Shopify Grow, Advanced or Plus. If unavailable, use a form app that supports the required JSON and API-key header, or have a developer connect the form through a server-side endpoint. Shopify Flow HTTP request documentation.

Optional alternative: Zapier

Use this only if you prefer an automation service or your existing native form integration requires it. Direct plugin and server-side routes above do not need Zapier. An automation subscription may add costs.

Connect your form using its supported Zapier integration, or send its webhook to a Webhooks by Zapier Catch Hook. Capture a test submission, then configure the outgoing request:

  1. After your form trigger, add Webhooks by Zapier → POST.
  2. Enter the PitchKraft endpoint and choose a JSON payload.
  3. Add the required and optional field keys listed above, selecting each value from the test submission. Keep the payload as one flat object.
  4. Under Headers, add Content-Type with application/json and X-Pitchkraft-Api-Key with your website’s key. Keep the key within the private automation settings.
  5. Test with a new email, confirm the saved contact in PitchKraft, then publish the automation. Webhook actions may require a paid Zapier plan.

Zapier’s outgoing webhook guide. Other automation tools can be used if they support the same POST, JSON, header and mapping settings.

For every platform, confirm the contact is in the correct website list and check the enquiry alert. A repeat email in the same website list updates the existing contact, and new enquiry notes can be appended. Test both new and repeat submissions; do not repeatedly retry failed requests without investigating the error. Our 24/7 support team can help choose and configure the right route: support@pitchkraft.ai.

Updated 3 November 2026

Let’s talk about your personalised outreach

Get in touch with our PitchKraft specialists to discuss your email personalisation and outreach requirements.

Send us a message

Phone Support