Integration setup checklist
To set up an integration in Tapmy, decide what it should do, connect the right provider account with the fewest permissions, and test one safe action in both Tapmy and the provider before you rely on it.
On this page
Applies to: creators connecting supported social, calendar, meeting, domain, payment or other outside services. Availability varies by setup and plan.
Plan the job first
Write down the outcome: publish to one account, read availability, route a domain or sync a defined record. Check who owns the provider account, what role you need, any existing automations, how sensitive the data is and whether an organization admin has rules.
Use an account you are allowed to manage. Note your Site, the provider account, what data flows where, the time and time zone, and how to roll back before you change permissions, DNS or connections.
How do I connect with the least access?
Authorizing is where checking starts, not ends. A healthy integration has an owner, scopes you understand, a passed test, monitoring and a clear way to reconnect or disconnect.
- Make sure the provider and the action you want are supported in your Tapmy setup. A logo in a list does not prove every action works.
- Choose the correct Site and provider account. Check the profile, workspace, organization, channel, calendar or domain before you approve.
- Read each requested permission. Grant only what the job needs, and stop if something looks too broad or unclear.
- Authorize on the provider's own domain. Never type credentials into a help article, screenshot or third-party form.
- Back in Tapmy, confirm the account name, connection status and any resources you can pick, such as channels or calendars.
- Run one test with fake data: one draft post, one time slot, one lookup or one non-destructive routing check.
- Verify the result in the provider, then confirm Tapmy shows the same object and state.
- Write down the owner, scopes, tested actions, renewal or expiry signs, monitoring and how to disconnect before you scale up.
How you know it worked
The right account is connected with sensible permissions, one test action works in both systems, and you know how to spot a failure, reconnect and disconnect without losing unrelated data.
An "authorized" badge does not prove that publishing, availability, data or routing works. Only the test does.
Common problems
- Authorization is denied. Check the provider account, your admin role, organization policy, pop-up blockers and the requested scopes.
- Connected, but nothing syncs. Check the direction, the object type, the selected resource, filters, time zone, provider status and the exact test time.
- Wrong account connected. Pause any automation, disconnect, revoke access at the provider if needed, then reconnect the right account.
Each provider has its own rules, rate limits, permissions, regions and outages, and Tapmy cannot guarantee a provider's uptime. Supported providers and sync actions vary by setup.
Change one thing at a time so you can undo it. Never share passwords, verification codes, API keys, tokens, DNS credentials, private calendar links, customer records or unpublished posts.
Next steps
Once the test passes, expand slowly, write a short reconnect guide and check what disconnecting would break before you depend on the integration for revenue.
If the test still fails, contact Tapmy Support with your Site, the provider, the affected object or public host, time and time zone, the exact error, what you expected and cleaned screenshots. If a credential was exposed, revoke or rotate it with the provider first.