Getting Help
When you need assistance with CustomJS and Make.com integration, there are several resources available to help you resolve issues and get the most out of your automation workflows.
Start with our comprehensive documentation:
- Integration guides for step-by-step setup instructions
- Code examples and templates for common use cases
- Best practices for optimal performance and reliability
- Troubleshooting guides for common issues
Connect with other CustomJS users:
- Community forum for discussions and questions
- User examples and shared solutions
- Tips and tricks from experienced users
- Feature requests and feedback
For technical issues and account-specific questions:
- Email support for detailed technical assistance
- Priority support for paid plan users
- Integration assistance for complex scenarios
- Custom development consultation services
To help us assist you more effectively, please gather the following information:
// Include the exact error message and context
const errorInfo = {
errorMessage: "The specific error message you received",
errorCode: "Any error codes displayed",
timestamp: "When the error occurred",
scenario: "Description of what you were trying to do"
};
Provide the JavaScript code that's causing issues:
// Your actual code (remove sensitive data)
const problematicCode = `
// Include the code that's not working as expected
// Remove any API keys, passwords, or sensitive information
`;
Share the structure of your input data:
// Example of the input data structure
const inputExample = {
// Show the structure of data you're passing to the module
// Use placeholder values instead of real data
field1: "example value",
field2: 123,
field3: ["array", "example"]
};
Describe what you expected to happen and what actually occurred:
const issueDescription = {
expected: "What you expected the code to do",
actual: "What actually happened",
impact: "How this affects your workflow"
};
If you're having trouble setting up the CustomJS integration:
- Verify your API key is correct and active
- Check that you're using the correct CustomJS module version
- Ensure your Make.com scenario permissions are properly configured
- Confirm your account has sufficient credits/quota
When your JavaScript code isn't working as expected:
- Review the troubleshooting guide first
- Check for syntax errors and missing return statements
- Validate your input data structure
- Test your code in the CustomJS platform before using in Make
If your scenarios are running slowly or timing out:
- Review code efficiency and optimization opportunities
- Check if you're processing large datasets appropriately
- Consider breaking complex operations into smaller steps
- Verify you're not hitting rate limits
To request new features or enhancements:
- Describe your specific use case and requirements
- Explain how the feature would benefit your workflows
- Provide examples of the desired functionality
- Include any relevant technical specifications
- Email response: Within 24-48 hours during business days
- Community forum: Community-driven, varies by activity
- Documentation updates: Ongoing based on feedback
- Email response: Within 4-8 hours during business days
- Critical issues: Same-day response for production problems
- Integration assistance: Dedicated support for complex setups
- Custom solutions: Consultation for specialized requirements
Search our knowledge base for:
- Frequently asked questions and answers
- Step-by-step tutorials for common tasks
- Video guides for visual learners
- Code templates for quick implementation
Access our collection of:
- Working code samples for various scenarios
- Integration patterns and best practices
- Template functions you can customize
- Real-world use cases and implementations
Comprehensive API reference including:
- Endpoint documentation with parameters and responses
- Authentication methods and security guidelines
- Rate limiting information and best practices
- SDK documentation for supported languages
When reporting bugs, please include:
const bugReport = {
title: "Brief description of the bug",
description: "Detailed explanation of the issue",
stepsToReproduce: [
"Step 1: What you did first",
"Step 2: What you did next",
"Step 3: When the bug occurred"
],
expectedBehavior: "What should have happened",
actualBehavior: "What actually happened",
environment: {
browser: "Chrome 91.0.4472.124",
makeScenario: "Link to scenario or description",
customjsVersion: "Version of CustomJS module used",
timestamp: "2023-XX-XX XX:XX:XX UTC"
},
additionalInfo: "Any other relevant details"
};
For critical issues affecting production workflows:
- Mark as urgent in your support request
- Include immediate impact assessment
- Provide workaround attempts you've tried
- Include contact information for immediate follow-up
Submit detailed feature requests including:
- Business justification for the feature
- Technical requirements and specifications
- Expected timeline and priority level
- Willingness to participate in beta testing
Popular feature requests may be:
- Shared with the community for feedback and voting
- Prioritized based on demand and feasibility
- Included in development roadmap planning
- Announced for beta testing when ready
Participate in beta testing for:
- Early access to new features
- Feedback opportunities to shape development
- Priority support during testing phases
- Recognition as a community contributor
- Provide exact error messages and codes
- Include relevant code snippets and configurations
- Describe your specific use case and requirements
- Share what you've already tried to resolve the issue
- Write clear, concise descriptions of your issue
- Use proper formatting for code and error messages
- Include screenshots or videos when helpful
- Respond promptly to follow-up questions
- Allow reasonable time for responses based on support tier
- Provide additional information when requested
- Confirm when issues are resolved
- Share feedback on the support experience
- Share solutions that work for your use cases
- Participate in community discussions
- Provide feedback on documentation and guides
- Help other users when you can
For critical production issues:
- Check the status page for known issues
- Review recent changes to your scenarios
- Implement temporary workarounds if possible
- Document the issue thoroughly
- Mark support requests as "Critical" or "Urgent"
- Include business impact assessment
- Provide direct contact information
- Follow up within reasonable timeframes
- Monitor official communication channels
- Implement contingency plans if available
- Document impact for post-incident review
- Provide feedback on resolution effectiveness
Getting effective support is a collaborative process. The more detailed and specific information you can provide, the faster and more accurately we can help resolve your issues and improve your CustomJS experience.