Special workflows for Google Ads.
Each scenario shows the trigger, the Volimox handoff, and the human checkpoint. These are concrete workflow blueprints, not a claim that every connection is live today.
Lead form to qualified conversion
Connect a qualified customer request to the campaign that generated it.
Starts when
A Google Ads lead form submission enters Volimox and passes the qualification rule.
Result
Advertising reports can reflect leads that became real operational opportunities.
Volimox workflow
- 01Volimox stores the campaign and source metadata with the lead.
- 02Volimox creates the next sales or dispatch task and records the qualification state.
- 03The marketing owner reviews the conversion event before it is sent back.
Human checkpoint
Conversion recording is gated by a verified lead state, not by a raw form submission.
Booking outcome to campaign update
Use a real booking or service outcome to improve campaign visibility.
Starts when
A sourced Volimox lead reaches the configured booked or completed state.
Result
Marketing optimization is based on a customer outcome instead of a click alone.
Volimox workflow
- 01Volimox resolves the original campaign and lead references.
- 02Volimox prepares the conversion record with the approved value and source.
- 03The owner reviews the event and authorizes the campaign update.
Human checkpoint
No campaign event is emitted for unverified or duplicate outcomes.
Supported triggers and actions.
A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.
Triggers
- Lead form submitted
- Conversion recorded
Actions
- Record conversion
- Find campaign
- Update lead source
Detailed connection code.
This server-side TypeScript reference follows the same connection → action → mapped input pattern used by modern automation platforms. Provider credentials remain inside the approved connection; browser code never receives them.
TypeScript · server only
Send an approved offline conversion
import { createZapierSdk } from "@zapier/zapier-sdk"
const zapier = createZapierSdk({
apiKey: process.env.ZAPIER_API_KEY,
})
export async function runGoogleAdsAction() {
const { data: connection } = await zapier.findFirstConnection({
app: "google-ads",
owner: "me",
})
if (!connection) {
throw new Error("No approved Google Ads connection was found")
}
const result = await zapier.runAction({
app: "google-ads",
action: "send_offline_conversion",
connection: connection.id,
input:
{
"customerId": "{{env.GOOGLE_ADS_CUSTOMER_ID}}",
"conversionAction": "{{env.GOOGLE_ADS_CONVERSION_ACTION}}",
"gclid": "{{lead.gclid}}",
"conversionDateTime": "{{lead.qualifiedAtIso}}",
"conversionValue": "{{lead.value}}",
"currencyCode": "USD",
"orderId": "{{lead.id}}"
},
})
return result.data
}Connection setup.
The setup path is specific to the provider. We will never ask you to paste credentials into a public page.
Google Ads OAuth
A reviewable connection, step by step.
- 01Google Ads manager access
- 02Choose customer account
- 03Review conversion and reporting scopes
This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.
Related apps