Connect Close to Myuser

Campaign replies and bookings become Close leads, notes and opportunities.

Close models everything around Leads (the company) with contacts inside them - Myuser speaks that dialect natively: replies and bookings from your campaigns become Close leads, logged notes, and opportunities.

What the integration does

• Leads + contacts: Myuser finds the Close lead by the contact's email; if none exists it creates the lead (company) with the contact and their email/phone inside it.
• Email + meeting logging: outreach emails and booked meetings are logged as notes on the lead, tagged with the Myuser campaign name.
• Opportunities: when a prospect qualifies, Myuser opens an opportunity on the lead in your first active status - and if the organization has no opportunity statuses at all, Myuser creates a "New" status automatically.
• Booking sync: meetings on your Close calendar (synced via Close's calendar integration) are picked up so campaign analytics show who booked.
• Master AI: ask "what's the status of ACME in Close?" and the AI reads the lead through this connection.

Total setup time: about 2 minutes.

Step 1 - Create an API key

1. Log in to Close.
2. Open Settings (gear icon) -> Developer -> API Keys - or go straight to https://app.close.com/settings/developer/api-keys/.
3. Click + New API Key, give it a name like Myuser, and click Create.
4. Copy the key now - Close shows it only once. It starts with api_.

Step 2 - Paste it into Myuser

1. In Myuser open Product Settings -> Integrations.
2. Scroll to Integrate into your CRM -> Close.
3. Paste the key in the Close API key field.
4. Click Test integration - Myuser verifies it live (reads your user profile, nothing is written) and saves the key automatically on success.

What to expect

• Close's native email sync may already log your emails if you connected your mailbox to Close; Myuser's notes complement that with campaign context (which sequence, which step).
• Meetings created by Myuser appear in the lead's activity timeline.
• Opportunities land in your default pipeline's first status unless your team changes it afterwards.

Troubleshooting

• Key rejected: keys are organization-scoped and can be deactivated from the same settings page - check it's active and copied in full (starts api_).
• Lead duplicates: Myuser always searches by contact email first (email_address query) before creating - existing leads are reused. If you see duplicates, the contact's email in Close differs from the one Myuser contacted.
• Meetings not syncing back? Booking detection reads Close's meeting activities - those exist when Close's own calendar sync is connected (Settings -> Email & Calendar). Without it, Myuser still logs the meetings it books; it just can't see meetings booked elsewhere.