Les grands esprits se rencontrent

Instead of requiring an Hubspot User to remember to navigate to a specific page to look for workflow errors, I would like to be able to make a task associated with the specific contact that generated the  error in the workflow.    There are likely many use cases of this.  Here's one specific use case I would like to see:   On this knowledge base page: Troubleshoot common workflow errors (hubspot.com) on of the common workflow errors is on Set Contact Property   After the action that is trying to set the contact property, I would like to be able to have a If/then path that would branch on "error generated by previous action".  If an error occured then I would create a task associated with that contact and assign it to the appropriate Hubspot User.   Another option would be instead of an if/then branch that the Set Property Action had a "What to do on Error" setting, which could include things like:   Create task,  then continue workflow Create task, then exit workflow Jump to this node in the workflow etc... Thanks for considering this idea! Iswari    ... Afficher plus

Whenever I'm checking a Company (for example) and I want to access a specific contact (let's say that it's the most important one), it's dificult to find it if there are more than 5 assigned to that specific company and the one I want was created long time ago.   I would have to click on "view all contacts" or "view all deals" and find it, which is time-consuming and annoying.   It would be nice to be able to Pin the most important Deal or Contact to the top of the list. ... Afficher plus

Currently, users are forced to select between either a contact property or a manually entered email address for an internal email recipient.  E.g. - A scoring workflow sends a score notification message. It should be sent to an owning user (stored as a contact property), and to a shared mailbox, entered manually. One would reference the property, and the other be the manually entered address. "Send to: {{ contact.product_owner_email }},{{ contact.master_owner_email }},ScoreAlerts@WidgetCo.com"   Why: In many cases, a user that should receive this kind of internal alert may be out of office, or otherwise unable to follow up on the internal email. There may also be instances where the property has no value on a given contact. Rather than have those internal emails fall into a "black hole", it would be beneficial to add a manual address to ensure the internal email is handled properly.    Value: Timely responses to internal emails and ensuring the emails receive proper follow-up is difficult to give a value to. It will vary depending on how critical the internal email is. A score notification from a high-priority lead will have a different value than a weekly summary.   While this idea applies to internal emails sent inside of workflows, the ideal resolution would be to allow contact properties to be used alongside manually entered email addresses wherever an address may be selected. ... Afficher plus

We have a connected team inbox in HubSpot and are using the email reply beta, which tracks & allows automation around replies to marketing emails as long as they are being sent to a connected inbox. I think it would be great, and hopefully not too challenging, to implement a workflow enrollment trigger for Activity > Email received in connected inbox (allow selection of which inbox). Then, I would use this to automatically add anyone who emails our team inbox to a specific Salesforce campaign (right now, we have to add people manually to a list in HubSpot that triggers a workflow to do this).  ... Afficher plus

Hi, we have developed a workflow for our sales department, where the goal is that customers book an appointment for a showcase with us. Now it would be ideal if the workflow continues automatically after this appointment. But you can only filter in the workflows if a form was filled out for the appointment booking and not by the date of the appointment (both as a start trigger and in the course of the workflow). ... Afficher plus

Hi - We use workflows to automatically update a contact's lead status using email subject lines. (Logic: These emails get sent anyway and it reduces the amount of manual status updating our team needs to do.) This works great... the first time they go through the process but it breaks if they become a repeat customer. Here's an example:   Ex: Julia submits the form (hidden field: set lead status to "new") She schedules an appointment with the company and is sent the confirmation email • confirmation email subject line + lead status (new) triggers the workflow to update the    In the future, Julia submits the form AGAIN (this happens a lot for us) • her lead status is changed in the form to "new" • because she already has a subject line on her record, the workflow would trigger and she'd be wrongly re-categorized as "with sales"   I've come up with some hacky-work arounds (like the example above, I layered on that to hit the workflow, the contact also needs a logged meeting set in the future). But I haven't come up with workarounds that work for everything.   A better solution would be a manual "reset" in a contact's communication history. Basically, I want to be able to say: Hubspot, don't look at any history before a given date. So the system would look at the contact like they're brand new (because, it's a new sales cycle) but we'd have all the existing communications for our record. ... Afficher plus

There needs to be an option in Workflows that allows for the assigned Contact Owner's HubSpot Signature to populate to Email Templates and Templates in Sequences triggered by the Workflow. This is a critical element impacting the overall effectiveness of this automation expansion.    Thank you! ... Afficher plus

Assign meeting bookings to different sales team based on specific conditions. For example, I would love if we can distinugish calls based on a  certainc condition that gets filled out on a form. ... Afficher plus

A lot of closed APIs require an IP to be allowlisted in order for it to grant access.   However, there's currently no way for these APIs to be used within HubSpot as there's no dedicated IP for API calls.   Making this happen would open a whole world of possibilities integration-wise.   (Also a lot of company's security protocols dictate that incoming requests have to be allowlisted) ... Afficher plus