Tally is often used for high-intent B2B forms: demo requests, event interest, partner applications, quote requests, and post-webinar surveys. Connecting Tally to Scribeless lets those submissions trigger handwritten follow-up automatically, so a strong lead can receive a personal note without manual exports or mail operations.

This guide uses Zapier as the example connector. The same campaign-first workflow can also be built in Make, Pipedream, n8n, or directly with the Scribeless API if your team prefers another automation layer.

Before you build the Zap, create the Scribeless campaign first. Choose the card or letter format, handwriting style, note copy, merge variables, return address, QR code or landing-page CTA, and approval settings. Zapier should add recipients to an existing campaign; it should not be where you decide the message strategy. That keeps brand, compliance, and measurement inside Scribeless while Tally remains the source of the lead data.

When someone submits a Tally form, Zapier catches the new submission and sends selected fields to Scribeless. Scribeless then adds the person to the campaign you choose. Common B2B examples include:

Tally works best for direct mail when the form intentionally collects the fields needed for sending. At minimum, collect first name, last name, company, address line 1, city, region, postal code, and country. If the form does not ask for a postal address, add enrichment or review before Scribeless.

For multi-step routing, add Zapier filters, delays, or Paths if your Zapier plan supports them. For example, you may only want to send notes for demo requests in target territories, enterprise company sizes, or submissions with a lead score above a threshold.

Use this structure for the first version:

Keep the first Zap narrow. Start with one form, one audience, and one Scribeless campaign. Once the data maps correctly, clone the Zap for other forms or add routing logic.

Create a new Zap and select Tally as the trigger app. Choose New Submission as the trigger event, then connect the Tally account that owns the form. Select the specific form you want to use for the automation.

Test the trigger with a realistic submission. A useful test record includes a real-looking company name, job title, email, phone number, full postal address, lead source, and the form answers you plan to use for qualification. This makes field mapping easier because Zapier can show the exact values you need to pass into Scribeless.

If fields are missing, submit the form again with every required field completed and retest the trigger. Zapier only shows fields that appear in the sample submission it has loaded.

Filters keep handwritten mail focused on the submissions most likely to justify a premium follow-up. Useful filters include form type, territory, company size, budget range, role, product interest, or a consent checkbox. For example, continue only when Form type is Demo request and Company size is greater than 50 employees.

Delays help when a sales or customer success rep should act first. You might wait two business days after a demo request, then send a note if the opportunity is still open. You can also delay event follow-up until after the event.

Zapier's guides for filters and delays are useful if you are adding these steps for the first time.

Add Scribeless as the action app and choose Add Recipients. Connect your Scribeless account, then open the action configuration. Select the campaign that should receive Tally submissions.

The campaign selection matters. Use a campaign built for the specific form intent, not a generic catch-all campaign. A demo request note should sound different from a partner application note or a customer survey thank-you. Keep the CTA aligned with the form: book the next call, review the proposal, visit a personalized landing page, or contact the assigned rep.

Map the required recipient fields first: first name, last name, company, address line 1, address line 2 if available, city, region or state, postal code, and country. Then map any fields your campaign uses as merge variables, such as company name, product interest, event name, sales owner, lead source, UTM campaign, or a short form answer.

Use stable Tally question labels before launching the Zap. If a field is renamed later, check the Zap again to make sure Zapier is still sending the expected value. Zapier's guide to mapping fields between steps helps when you need to select nested submission answers or reuse data from earlier steps.

Send one internal Tally submission through the full Zap. In Scribeless, confirm that the recipient was added to the correct campaign and that each merge variable is populated cleanly. Check address formatting, capitalization, company name, and any note personalization before enabling the automation.

If the test looks right, turn on the Zap and monitor the first live submissions. For teams using direct mail in sales or marketing operations, consider notifying the campaign owner when a recipient is added. That gives reps visibility into physical follow-up without asking them to manage the mailing process.

If Tally fields are missing in Zapier, submit a complete test response and retest the trigger. If the Scribeless campaign is not available, confirm that you are connected to the correct Scribeless account and that the campaign has been created before building the Zap. If a recipient is rejected, check address completeness and country formatting first. If too many submissions qualify, add a filter before Scribeless so only the right B2B leads receive handwritten follow-up.