Your tools. The access the job actually needs.
Built around the software and way of working you already have. We assess the exact task, account, and permissions before agreeing on a connection.
Concept illustration
Connected, with clear boundaries.
Your business systems remain the source. The agent gets the access needed for the agreed internal job.
- 01Check permissions
- 02Prepare the work
- 03Keep people in control
Compatibility is a check, not a logo
A product name alone does not tell us whether your workflow will work. Your plan, account permissions, data format, and the provider's rules all matter. The same software can support one task and restrict another.
The categories below are assessment areas, not a list of certified or prebuilt Puestario integrations. A connection is called tested only after the agreed task works with the approved account and its result has been reviewed.
Files and shared records
Check folder permissions, readable formats, source links, and which copy is authoritative.
Calendars and task lists
Check whose calendar is in scope, the time zone, and whether the job reads, drafts, or updates.
Business systems
Check the exact CRM, accounting, inventory, or freight workflow, including available APIs, exports, and account restrictions.
Read, prepare, or change
- 01Your team asks
Through an approved channel that permits the intended use.
- 02Access is checked
Who is asking? Which records and actions are allowed?
- 03The agent prepares
Reads approved sources and prepares the scoped task.
- 04People review
A useful answer, an exception, or an allowed internal update.
The standard desk does not contact customers or move money. An approval does not expand the agreed scope.
Conceptual workflow. Each account, connection, and action must be assessed and agreed. Cloud processing may be involved.
- Read: retrieve only the records the task needs and show when they were checked.
- Prepare: create a draft, summary, or exception list for a person to review.
- Change: allow only the specific internal actions written into the scope. An approval does not add a new capability or override a platform rule.
- The standard desk does not contact customers, pay, refund, or transfer money.
Choose a connection that can be maintained
An official API or supported connector is often the first option to assess. An approved export may be enough for a scheduled report. Browser access needs a separate check of permission, reliability, and changes to the interface.
We document the source, account owner, permitted actions, refresh schedule, and what the agent does when access fails. We do not ask you to paste passwords into a public form.
Messaging is one part of the workflow
The messaging channel is agreed after checking the exact product, account, and integration. WhatsApp’s Business Terms say its Business Services are not intended for intra-company use. A WhatsApp illustration does not confirm that your internal workflow is permitted. Check the applicable terms before choosing a channel; Puestario does not promise an official partnership or permanent access.
The job, records, and schedules should have a recovery plan if the channel changes. Moving to another channel requires testing identity, permissions, and delivery; changing a phone number does not solve those questions.
Know where information goes
Source records remain in the approved accounts.
Runs the agreed workflow. May hold working files and logs.
Models and connected services may process approved information.
Locations, access, retention, and backups are agreed before installation. On-site equipment does not mean all processing stays on-site.
The source records remain in your business systems, but the workflow may create logs, working files, and backups. Approved content may be processed by cloud models or connected providers. Agree on those locations, access, and retention before installation.
Each company needs its own access and records. Within the company, an owner-only financial brief and a staff task list need separate permissions. A dedicated machine helps separate clients; it does not replace access controls.
What to bring to the assessment
- One task, a responsible person, and a sample of the expected output with sensitive details removed.
- The names and plans of the systems involved, plus the person authorized to grant access.
- Rules for records, staff roles, approvals, schedules, and handling failures.
- A written plan identifying approved services, access, support, and responsibilities.
What our internal examples establish
An integration is scoped by its task and permissions, not just its software logo. The Son Hábitos material supports the distinctions below. It does not establish compatibility with every account or software version.
| Workflow | Evidence available |
|---|---|
| WhatsApp → Emily → approved records | Owner-supplied screenshots show requests, responses, a displayed database query, and a follow-up record summary. They do not independently prove every database operation. |
| Trainerize → synchronized data | Emily describes a synchronization feeding the reporting database. The connector configuration, freshness checks, and recovery procedure still require technical verification. |
| Meta Ads → SPARX report | SPARX describes scheduled campaign reports with human decisions afterward. The underlying API responses and delivery logs were not included in the supplied evidence. |
Before connecting your account
Confirm the exact read and write actions, account permissions, data freshness, failure handling, and a sample output. Test those actions with your source before calling the connection ready. Broader access needs a separate decision.
Read the operating case ↗