GitHub Actions were introduced in 2019 to increase workflow velocity and add customized automation to the repositories. In addition, GitHub introduced its own marketplace for promoting, commercializing, and sharing these automation tools, which currently hosts 16,730 Actions. Further, there are numerous Actions that are developed and distributed in local repositories and outside the marketplace. So far, the research community conducted mining studies to understand GitHub Actions with a significant focus on CI/CD. We performed a survey study with 90 Action developers and users of GitHub Actions to understand the motivations and best practices in using, developing, and debugging Actions, and the challenges associated with these tasks. We found that developers prefer Actions with verified creators and more stars when choosing between similar Actions, and often switch to a different Action when an Action has bugs, is not properly documented, or another Action of better quality is available. Developers choose to develop new Actions rather than using the existing ones mainly when there is no existing Action for their task or the existing Actions are limited in functionality. 60.87% of the developers consider the composition of YAML files challenging and error-prone and mostly check Q/A forums to fix issues with these YAML files. Finally, developers tend to avoid using Actions to reduce complexity, and security risk, or when the benefits of Actions are not worth the cost/effort of setting up Actions for automation.