การเชื่อมต่อและยืนยันตัวตนของแอป

An automation platform like Zapier or Make can only move data between your apps if those apps grant it access. Before any workflow runs, you must connect each app you want to use.

A connection tells the platform: it is allowed to read from or write to this account on your behalf.

A connection is a stored, authorized link between the automation platform and one of your accounts — for example your Gmail, your Slack workspace, or your CRM.

Once made, you can reuse the same connection across many workflows without logging in each time.

Most popular apps use OAuth. When you connect, a pop-up takes you to the app's own login page where you approve access. The platform never sees your password.

OAuth returns a secure token the platform uses instead of your credentials.

Some apps instead give you an API key — a long secret string you copy from the app's settings and paste into the platform.

API keys are simpler but more sensitive: anyone holding the key can act as you, so treat them like passwords.

You may also encounter:

• Basic auth: a username and password pair
• Token plus secret: two values used together
• Custom headers: for APIs with their own scheme

The platform tells you which fields each app requires.

When building a step, you choose an app and click to add a connection. Follow the prompts to log in or paste credentials, then the platform verifies access.

A green checkmark or success message confirms the connection works.

OAuth connections request scopes — specific permissions like read email or send messages. Approve only what the workflow truly needs.

Granting minimal scopes limits the damage if a connection is ever compromised.

If you manage several accounts of the same app, give each connection a clear name like Sales Gmail or Support Gmail. Good naming prevents sending data to the wrong account.

Reusable connections keep your workflows tidy and consistent.

Connections can stop working if a password changes, access is revoked, or a token expires. The platform usually flags the broken connection and pauses affected workflows.

Reconnecting the app restores access and resumes your automations.

Protect your connected accounts:

• Use minimal scopes and revoke unused connections
• Never share API keys in screenshots or chats
• Enable two-factor authentication on the underlying apps
• Periodically review which platforms have access

Both Zapier and Make have a connections or apps screen where you can view, rename, reconnect, or delete every connection in one place. Reviewing it regularly keeps your account clean and secure.

You learned how to connect and authenticate apps:

• Connections authorize the platform to act on your accounts
• OAuth is secure and password-free; API keys are simpler but sensitive
• Grant minimal scopes and name multi-account connections clearly
• Reconnect when connections break and review access regularly

Secure connections are the foundation of every reliable automation.