Supported Plans
We support both the Professional and Business plans.
Integration with Copper
Access: Jiminny uses the Copper REST API to access your data through an API token. Generate this token during onboarding by following these steps:
In the Copper web application, navigate to Settings > Integrations > API Keys.
Click Generate API Key and label the key as Jiminny.
API Limits: Copper imposes strict API limits. Jiminny minimizes resource use through caching and maintaining a shadow copy of some data, typically resulting in about 500 API calls per day per user. This can vary based on activity levels on the platform.
Data Synchronization
Types of Information Sent: Jiminny can create Activity and Task records in Copper. Optionally, Lead Statuses and Opportunity Stages can also be updated through activity log workflows.
Task vs Activity:
Link to Task: Closing a task in Copper and associating it with a logged call/meeting.
Standard Logging: Creates an activity. If a follow-up is created, it generates a new task.
Storage in Copper: Data is stored under Leads, People, Companies, or Opportunities, depending on the related activity.
Record Matching: Records are matched based on email addresses and phone numbers. This happens automatically during:
Scheduled meetings.
Ad-hoc conferences.
Calls or texts initiated through our Chrome Extension.
Known Limitations:
Full names are required for matching customers when logging activity.
Custom fields are supported only in the Follow-up section of activity logs.
Integrating Copper with Jiminny
Invite the Copper admin to Jiminny.
After the admin selects their roles and completes the setup, they should provide the API key to our engineers.
This must be done at least 24 hours before the technical setup is completed.
This streamlined article eliminates redundancy and organizes the information more effectively for better readability and comprehension.