Metaforce Zapier integrationAutomate Metaforce with Zapier.
The Metaforce Zapier integration gives you 1 trigger, 2 actions and 0 searches. An instant trigger reacts when someone submits a Smartform, one action sends a Smartform to recipients, and the other fetches a file that came in with a submission.
Verified Trustpilot reviews · AI, automation & growth agency
What the Metaforce Zapier integration does
Metaforce builds polished documents from your data, and its Smartforms are the forms people fill in and send back. On Zapier, it lets a Zap (the automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens) react to a submitted Smartform, send one out, or pick up a file someone uploaded with it.
Every submission in a shared sheet. New Smartform Submitted starts the Zap as soon as an answer comes in, and a spreadsheet step adds a row with what you choose to keep. Your team reads the sheet; nobody exports anything.
A Smartform that leaves on its own. When a contact appears in another tool, Send Smartform sends the right Smartform to that person, with the options you set in the step and the Secret the step requires.
The uploaded file filed where it belongs. Get File Submitted to Smartform fetches a file attached to a submission, and a later step can drop it into the storage tool your team already uses.
Know the limits too. Smartforms are designed in Metaforce, and a Zap only picks them. With no search step, a Zap never pulls up an older submission. And anything submitted before the Zap was published never starts it. The trigger also watches only the SmartForm picked in its required field. For more, see our Zapier review.
Zapier words in one minute
Eight terms come back across this page. Here they are in plain words.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. For Metaforce, it is a Smartform being submitted by someone.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like sending a Smartform.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts tasks, not Zaps or triggers.
- Instant vs polling trigger
- An instant trigger is reported by the app the moment the event happens; a polling trigger is checked by Zapier on a timer. Metaforce's trigger is instant.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
- Connection
- Your Metaforce account linked to Zapier once, then reused by every step that uses the app, trigger and actions alike.
What it really costs you
Zapier bills in tasks. New Smartform Submitted never costs one, however many forms come back.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on the free plan
Each Send Smartform or Get File Submitted to Smartform that succeeds counts as one task, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each held to two steps. Fetching a file and then storing it is two actions, so a multi-step Zap, which needs a paid plan, as does any filter. Metaforce is not a premium app. The grid below is the polling interval by plan; it does not apply to this app's instant trigger.
Connect your Metaforce account
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. Type Metaforce in the search box of the dialog, pick it from the list, then click Add connection.
- 02
Sign in and grant access
A tab opens on Metaforce. Sign in there and grant Zapier access to the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 03
Reuse it in every step
The account is now linked to Zapier once. New Smartform Submitted, Send Smartform and Get File Submitted to Smartform all rely on that same connection, in this Zap and the next ones.
Your first Zap: keep every file people upload
GoalEach time a Smartform comes back with a file, fetch that file and save it in your storage tool.
- 01
Build the trigger
Start a new Zap, choose Metaforce as the app that starts it and New Smartform Submitted as the event, select your connection, then pick the SmartForm to watch.
- 02
Test on a real submission
Run the trigger test. Zapier brings back the three most recent items of the connected account, so you read what a real submission carries before mapping anything.
- 03
Fetch the file
Add Get File Submitted to Smartform. It needs three values: DialogFormId, FileuploadProperty and FileId. Map them from the trigger if the test shows them there; check at the test which ones arrive.
- 04
Store it
Add your storage tool with its upload action and map the file from the previous step. This second action makes the Zap multi-step, so it needs a paid plan.
- 05
Test and publish
Test each action once and read what came back, then publish the Zap to switch it on. Each submission will cost two tasks. For a guided start, see our Zapier training.
The trigger
1 event starts a Zap when something happens in Metaforce, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Smartform Submitted
Instant triggerIn Zapier“Triggers when a Smartform is submitted.”
Starts your Zap each time someone submits the Smartform you picked, and passes that submission to the steps you add after it.
The actions
Metaforce gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Smartform
ActionIn Zapier“Send Smartform to recipient(s).”
Sends one of your Smartforms to its recipient or recipients, so they can fill it in without you mailing anything by hand.
Get File Submitted to Smartform
ActionIn Zapier“Get file submitted to Smartform”
Fetches a file that someone uploaded with a Smartform submission, so the next step can store it, forward it or attach it elsewhere.
When it breaks
Zapier links no help article to Metaforce. What follows is how every Zap behaves, plus what the Metaforce steps require themselves.
Four cases are worth checking before you blame the app. If a Zap still misbehaves, see our Zapier troubleshooting guide.
Nothing from before the Zap
A Zap only reacts to Smartforms submitted after you switch it on. Older submissions are never picked up; moving that backlog is a separate job.Three identifiers for one file
Get File Submitted to Smartform requires DialogFormId, FileuploadProperty and FileId. Map all three, and check at the test that each one carries a value.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your task count. Check where each action writes.A sudden flood held back
After a bulk import or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection.
Need help automating Metaforce with Zapier?
A person reads every message.
