Start with a supported recipe in your Studio workspace. For a client’s external systems, use the implementation brief to configure and test their own authorized connections.
Your first working recipe
Enable the rule below with the referral source selected, then start a new client workflow in the lab. Recova creates a delivery contact and an assigned follow-up task. Check the run here and complete the task in your delivery desk. Reopening the same prospect does not import it twice.
A simple rule handles assignment and creates a follow-up task as the lead is saved.
Loading automation settings…
Choose the tools your client actually needs.
Connect apps with Make
Use the client’s own Make organization for external multi-step workflows. Create a scenario with a test input, map only the required fields, configure the destination connection, add duplicate protection and a failure route, then run it once with synthetic data. Verify the destination before scheduling it.
Recova provides the brief and delivery checklist. A live Make connector and embedded builder are not included here. Make usage and hosting are separate.
Agree the trigger, inputs, owner, output and excluded actions.
Connect only accounts the client authorized. Keep credentials out of transcripts.
Test a normal input, a duplicate, a missing required field and an unavailable destination.
Check the resulting record or task in the actual destination. Save that evidence with the engagement.
Agree monitoring, usage budget, failure owner and a pause procedure.
Have the client accept the result before enabling live traffic.
Make the price match the work
Separate implementation, recurring operation and variable provider usage. Estimate the benefit from the client’s evidence, label assumptions and verify them in a pilot. Agree currency, included usage, support and a review date. Your proposal can be tailored; your Studio membership does not set your client’s price.