Skip to content
GuideForCan useWith or without Foxden AdminNeedsemail

Send responses to your team and tools ​

This page shows you how to send each response of a form on: as an email to your team, as an auto-reply to the respondent, as a lead in Fennec, or to a webhook. It also covers the notifications each person gets in Pampas.

Each of these is a destination, set per form on the form's Destinations page.

Before you start ​

  • Email notifications and auto-replies need email set up on the server. Until it is, Pampas sends no email: each email delivery is recorded as Cancelled with the note that no mail service is set up. See Set up email.
  • A Fennec destination needs Fennec paired with Pampas. On a server where the apps were installed together this is done already; otherwise see Set up Pampas for your team.

Add a destination ​

  1. Open the form and select Destinations.
  2. Select Add destination and pick a kind: Email notification, Auto-reply, Webhook or Fennec.
  3. Fill in the dialog (see the sections below) and select Create destination.

A destination works from the next response on. To pause one, select Disable; Enable turns it back on.

Email your team about each response ​

In Email notification:

  1. In To, type up to 10 addresses, one per line.
  2. Optionally type a Subject. Leave it empty for the default, New response. You can show an answer in the subject, such as @{field.company|New response}.
  3. Optionally pick a Reply-To: an email question on the form, so that replying to the notification writes to the respondent.
  4. Choose a Frequency: Immediate (one email per response), Hourly digest or Daily digest.

Reply to the respondent ​

An Auto-reply thanks the respondent by email. Its subject is the form name followed by "We received your response", and it names your company.

  1. In Email field, pick the email question the reply goes to. The form needs one first.
  2. Tick Include answers to copy their answers into the email.
  3. Tick Include rights link to add the private link where they view, edit or delete their answers.

The dialog warns that the typed address is not verified: a typo sends the answers, and the link to change them, to a stranger. Pampas therefore sends an auto-reply only when one of these is true for the response:

  • The form asks for a captcha (Every submission or When something looks off under Share › Access) and captcha keys are saved on the server. The mode is enough: the respondent does not have to have seen a challenge.
  • The response is Email-verified: the respondent was invited with Email code access and entered the code. The reply then goes to that verified address, not to the answer in the email field.

When neither is true, the form's responses create no auto-reply at all, and the delivery log shows nothing for it.

An auto-reply also is not sent:

  • when the response is an edit or a deletion; only a new submission gets one.
  • while the response is held as suspected spam. It goes out if you accept the response.
  • a second time to the same address for the same form within an hour. The delivery shows Failed.
  • when the answer is empty or not a plain email address. The delivery shows Failed.
  • when no email service is set up on the server. The delivery shows Cancelled.

Create a lead in Fennec ​

In Fennec, map the form's questions to the lead's fields: name or first name and surname, email, company, phone, job title and the others listed. Answers you do not map are added to the lead's message.

Each response then opens a lead in Fennec, and Fennec takes it from there. When a response is deleted in Pampas, Fennec gets a note of the deletion. See Fennec, the CRM for what happens to the lead.

Post responses to a webhook ​

In Webhook, type the receiver's public https address in URL and tick the Events to send: a response is submitted, edited or deleted, or an invited person opens the form or starts answering. Pampas signs every post. The secret is shown once when you create the destination: copy it then. Rotate secret makes a new one and stops the old one at once.

Private and local addresses are refused. For the payload, the signature check and retries, see the Pampas API page.

Test and watch deliveries ​

  • Send test sends a sample to a webhook or Fennec destination. Tests are not added to the delivery log.
  • Each destination's Delivery log shows the latest 50 deliveries with their status: Waiting, Sending, Delivered, Failed, Gave up or Cancelled. Select Replay to send a finished one again.
  • Delivery at a glance counts what was delivered and what failed in the last 24 hours.

A delivery that fails is tried up to eight times in all, with a growing delay, and shows Gave up after the last try. A destination that has failed 20 times in a row is tried once a day until it works again. A webhook receiver that answers HTTP 410 turns its destination off; select Re-enable once the receiver is back.

Choose your own notifications ​

Pampas also tells people about forms in the bell: new responses, invited people who finished, suspected spam, forms that filled up, and destinations that gave up. Only people who can manage Pampas and the person who created the form get these.

  1. Open the bell and its settings.
  2. For each topic, keep it in the bell or not, and choose to get an email at once or never.

Every topic starts in the bell with email off.

People who can manage Pampas also get one email a day, when there is something to report: deliveries that failed, responses respondents deleted, a form that got busy enough to ask for a captcha, the daily email limit reached, or uploads nearing the server's limit.

Troubleshooting ​

The auto-reply never arrives ​

Check the three conditions above: a captcha mode with keys saved, or an email-verified response; email set up on the server; a plain address in the chosen email question. If the delivery log shows nothing for the response, the captcha or verification condition was not met.

"Pair Fennec in Settings first." ​

Fennec is not paired with Pampas. Someone who can manage Pampas pairs it in Settings, or connects the apps in Foxden Admin.

"The test lead has no email. Map an email field first." ​

Map an email question to the lead's email in the Fennec destination.

"Delivery stopped: the receiver answered that this address is gone (HTTP 410)." ​

The webhook receiver said the address no longer exists. Fix the receiver or the URL, then select Re-enable.

"Private and local addresses are blocked on this server." ​

Webhooks go only to public https addresses. Use the receiver's public address.

Email notifications show "Cancelled" ​

No email service is set up on the server, so nothing was sent. Ask whoever runs the server to set up email, then select Replay on the deliveries you need.

Foxden is open source under Apache-2.0.