Setting things up

What you need first

1. A Meta Business account with a verified business.
2. A WhatsApp Business Account (WABA) with a phone number added. The number must not be in use on the normal WhatsApp or WhatsApp Business app — Meta will ask you to remove it there first.
3. A permanent access token — Meta → Business Settings → System users → add a system user, give it the WhatsApp permissions, then generate a token. A temporary token expires in 24 hours and your flows stop; use a permanent one.

Then, in Yantra

1. Open Apps → Connect and choose WhatsApp.
2. Paste the Phone number ID (Meta → WhatsApp → API Setup) and the permanent token.
3. Paste the App secret from Meta → App → Settings → Basic. This is what proves an incoming message really came from Meta. Without it we turn incoming messages away, so replies never arrive and no flow waiting on a message ever starts.
4. Yantra checks them against Meta before saving. If the keys are wrong it says so and saves nothing.
5. Open Inbox. It shows a Callback URL and a Verify token.
6. In Meta → WhatsApp → Configuration → Edit, paste both, and subscribe to “messages”.

1. Meta → WhatsApp → Message templates → Create.
2. Write the message with numbered blanks: Hi {{1}}, your appointment is at {{2}}.
3. Pick the right category. Utility for reminders, receipts and order updates; Marketing for offers. Getting this wrong is the usual reason for rejection.
4. Approval is usually minutes, sometimes a day.
5. In Yantra, put the exact approved name in the step, and fill the blanks in order — the first value goes into {{1}}, the second into {{2}}.

1. Open the flow, click the trigger step. Its address is right there — copy it.
2. Paste it into the other tool as a webhook / callback URL.
3. Publish the flow. Before you publish, anything sent is recorded but does not start it.
4. Send one test entry from the other tool, then use What has arrived? on the trigger step to see exactly what turned up.

That last step matters: “nobody has called it yet” and “it is being called and refused” look identical from outside, and they need completely different fixes.

Reading the data

Whatever was sent is available as {{trigger.something}} — so a form field called phone is {{trigger.phone}}. Set Where is it coming from on the trigger to Meta Lead Ads, Razorpay, Shopify or IndiaMART and Yantra tidies their format into plain fields first.

1. Open Settings → Tally and copy the setup command.
2. Run it on the Windows machine where Tally is open. It installs a scheduled task that keeps running after a restart.
3. In Tally, ODBC/Gateway must be on — Tally is listening on port 9000 by default.
4. Come back to Settings → Tally. Once the agent has said hello, the company name appears.

Then flows can post a sales voucher, receipt, payment or ledger, and read ledgers or outstanding bills. Party names must match your Tally ledger names exactly.

1. Google Cloud → create a service account → make a JSON key.
2. Paste that JSON into Yantra under Apps → Google Sheets.
3. Share the sheet with the service account's email, as Editor. This is the step everyone forgets — without it Google refuses, and the run says the sheet was not found.
4. The Spreadsheet ID is the long code in the sheet's URL, between /d/ and /edit.

1. Razorpay Dashboard → Settings → API Keys → generate a key.
2. Paste the Key ID and Key Secret into Yantra under Apps → Razorpay.
3. A Collect payment step then creates a payment link with the amount already filled in — send it on WhatsApp in the next step.

• Open the run. Runs → click any row. You see every step, what it was given, what came back, and which one stopped — plus the steps the run never reached.
• Carry on from the failed step. Fix the setting, then use that button rather than “Start over” — starting over runs every step again, so a message that already went out goes out a second time.
• Test one step. In the builder, Test this step runs just that step using the data from the last real run. A step that sends really sends, so it asks first.
• It retries itself. A timeout or a “too many requests” is retried with a growing gap. Wrong credentials are not retried — the app is flagged instead, because trying again cannot help.
• A failed run is not billed. Only successful runs count against your plan.

WhatsApp (your own WABA) · Razorpay · Google Sheets · Tally · Shiprocket · MSG91 (SMS) · Yantra's own tables, contacts and documents · and HTTP request, which reaches any system with an API and a key.

That is the whole list. We would rather name nine that work than five hundred that do not. Something missing? The HTTP request step covers most of it today — and tell us what to build next.