--- title: "Partner applications into Salesforce" description: "Send partner and vendor applications to Salesforce as structured records assigned to a review queue, instead of leaving them in an email thread." url: "https://www.formformform.com/automations/salesforce-partner-applications-triage" type: static generatedAt: "2026-08-23T18:56:58.727Z" --- ![Salesforce logo](/logos/integrations/salesforce.ico) # Route partner applications into a review queue Partner and vendor applications land in Salesforce as records in a review queue, not as forwarded email. When this happens New submission on your partner or vendor onboarding form Do this Create a Lead or custom object record in Salesforce with the application details One-directional. A submission triggers the action — nothing is written back into your form. Partner applications are read by two or three people who are not in the sales pipeline every day. Left in a mailbox, nobody can tell which have been looked at, and the same applicant gets a reply twice or not at all. Partnerships teams use this to give applications the same shape as everything else in the org: an owner, a status and a date. A queue view shows what is waiting, and the reviewer reads the whole submission on the record rather than scrolling a forwarded thread. ## Setting it up 1. 1 Decide the object before touching Zapier. A Lead with a partner record type works when partners eventually become accounts; a custom Partner Application object is better when the review has stages of its own. 2. 2 Publish the application form with Organization / Company required, since it becomes the record name under either design. 3. 3 Point the "New Submission" trigger at the application form and pull a sample with every long answer filled in, so you can see how much text Salesforce has to hold. 4. 4 Add the Salesforce Create Record action and select the object you settled on in the first step. 5. 5 Map Organization / Company to Company on a Lead, or to the record name on a custom object, and split Your Name across the first and last name fields. 6. 6 Map Partnership Type to a picklist on the record so the queue can be filtered and reported on by the kind of partnership being proposed. 7. 7 Set the record owner to the partnerships queue rather than the integration user, otherwise every application is owned by the account running the Zap and nobody sees them in a list view. 8. 8 Send a test application, check it lands in the queue view the reviewers actually open, then turn the Zap on. ## What maps where Using the [Partnership Inquiry Form](https://www.formformform.com/templates/partnership-inquiry-form) as the starting point. These are its real fields — swap in your own and the mapping works the same way. Form field Salesforce Your Name Split across first and last name on the record Organization / Company Company on the Lead, or the record name on a custom object Email Address Email, the field duplicate checks compare Website Website on the record Partnership Type Picklist used to filter the review queue Tell Us About the Opportunity Description, the long field reviewers read first ## Variations worth knowing Give each partnership type its own reviewer Partnership Type is answered on the form. Zapier paths can set a different queue or owner per type, so reseller applications reach one reviewer and technology partners another, without somebody triaging the list by hand every morning. Surface the goals answer in the list view "What Are You Hoping to Achieve?" decides most applications. Map it to its own long text field rather than appending it to the description, so reviewers can add it as a column in the queue view and sort out the obvious mismatches before opening anything. ## If something isn't arriving Long answers arrive cut short on the record. The Salesforce field is a 255-character text field. Change it to a Long Text Area in Setup and re-map it in the Zap. Text already truncated cannot be recovered from Salesforce, only from the original response in formformform. Applications are created but nobody is told. Creating a record raises no alert on its own. Add a queue email in Salesforce, a Flow that posts on record creation, or a second Zapier action into whichever channel the partnerships team actually watches during the day. ## Frequently asked questions Should partner applications be Leads or a custom object? A Lead suits partners who convert into accounts and opportunities like any other deal. A custom object earns its keep when the review has its own stages, or when applications would otherwise clutter the sales team's lead views and reports. Can an applicant change what they submitted? No. A submission is a record of what was sent, and nothing is written back into it from Salesforce. If details change, ask for a fresh submission or have the reviewer update the Salesforce record directly and note the change there. How do we keep applications out of the sales lead queue? Set a partner record type or a distinct source value at creation, then build sales list views to exclude it. Reviewers get their own queue filtered on the same field, so each team sees only the records it owns. ## Related automations - [Add webinar registrants to a Campaign](https://www.formformform.com/automations/salesforce-webinar-signups-to-campaigns) Webinar registrations create or update a Contact and add that person to the right Campaign as a member. - [Create a Lead from every demo request](https://www.formformform.com/automations/salesforce-demo-requests-to-leads) Each demo request becomes a Salesforce Lead with source and company filled in, ready for an SDR to work. - [Log quote requests as pipeline Opportunities](https://www.formformform.com/automations/salesforce-quote-requests-to-opportunities) Inbound quote requests arrive as Opportunities at the right stage, with budget and scope already on the record. - [Open a Case from every help request](https://www.formformform.com/automations/salesforce-help-requests-to-cases) Submissions on your help form open a Salesforce Case with priority and origin set for assignment rules to route. - [Write NPS scores onto the customer record](https://www.formformform.com/automations/salesforce-nps-scores-on-contacts) NPS responses update the matching Salesforce Contact, putting the score and the comment on the customer record. - [Add newsletter signups to Zoho CRM as tagged contacts](https://www.formformform.com/automations/zoho-crm-newsletter-opt-ins-tagged) Every newsletter opt-in becomes a Zoho CRM contact carrying a tag you can build a campaign list from. - [All Salesforce integration details →](https://www.formformform.com/integrations/salesforce) - [Start from the Partnership Inquiry Form →](https://www.formformform.com/templates/partnership-inquiry-form) - [Browse every automation →](https://www.formformform.com/automations) ## Build the form first The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow. [Start free](https://app.formformform.com/register?utm_source=landing&utm_medium=bottom&utm_campaign=automations&utm_content=salesforce-partner-applications-triage)